Date: Sat, 02 Mar 2024 05:03:34 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 277414] FAT SecPerClust=128 can cause crash Message-ID: <bug-277414-3630-89ZGrpRQeq@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-277414-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-277414-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D277414 --- Comment #1 from commit-hook@FreeBSD.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3D7e4ac11b6076e6a9bf7341ddeae227842= 84ed733 commit 7e4ac11b6076e6a9bf7341ddeae22784284ed733 Author: Konstantin Belousov <kib@FreeBSD.org> AuthorDate: 2024-03-02 04:58:57 +0000 Commit: Konstantin Belousov <kib@FreeBSD.org> CommitDate: 2024-03-02 05:02:55 +0000 getblkx(9): be more tolerant but also strict with the buffer size checks It is possible that on-disk filesystem format causes allocation of buffers of size larger than maxbcachebuf. Currently, getblkx() and indirectly bufkva_alloc() panic in that situation. It is more useful to return an error instead, allowing the system to continue running. PR: 277414 Reported by: Robert Morris <rtm@lcs.mit.edu> MFC after: 1 week Sponsored by: The FreeBSD Foundation sys/kern/vfs_bio.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-277414-3630-89ZGrpRQeq>