summaryrefslogtreecommitdiff
path: root/rust/zerocopy/src/pointer/git@git.tavy.me:linux-stable.git
diff options
context:
space:
mode:
authorChristian Brauner <brauner@kernel.org>2026-05-11 15:41:41 +0200
committerChristian Brauner <brauner@kernel.org>2026-05-21 13:39:36 +0200
commitd90e60ced4c3c7cd55ba0bedcedd1090d0172ce0 (patch)
tree3510ae743e24e6f7b4da2ce137af6551d2977993 /rust/zerocopy/src/pointer/git@git.tavy.me:linux-stable.git
parentccde023e6aea3c31fb2643cb76a6205bc343f979 (diff)
parent18c3d6fcb557f920c9143711497625e70153874c (diff)
Merge patch series "fix crashes when mounting legacy file system with sector size > PAGE_SIZE"
Christoph Hellwig <hch@lst.de> says: Due to an almost comical failure on my part, my work in progress test case failed to create any file system on a 64k block size loop device, and then tried to mount it, leading to a probe of file system built into my kernel. Roughly the first half of the series are file systems that actually crashed, but I fixed up all the pattern of missing error handling that I saw. * patches from https://patch.msgid.link/20260511071701.2456211-1-hch@lst.de: omfs: handle set_blocksize failures ntfs3: handle set_blocksize failures minix: handle set_blocksize failures isofs: handle set_blocksize failures affs: handle set_blocksize failures befs: handle set_blocksize failures jfs: handle set_blocksize failures qnx4: handle set_blocksize failures hpfs: handle set_blocksize failures bfs: handle set_blocksize failures Link: https://patch.msgid.link/20260511071701.2456211-1-hch@lst.de Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'rust/zerocopy/src/pointer/git@git.tavy.me:linux-stable.git')
0 files changed, 0 insertions, 0 deletions