Syzbot CI

Subject	fs: don't set SB_RDONLY after filesystem errors
Author	brauner@kernel.org
Date	2026-10-29 16:06:52 +0000 UTC
Version
Cc	brauner@kernel.org code@tyhicks.com ecryptfs@vger.kernel.org exfat@lists.linux.dev farhad.alemi@berkeley.edu gfs2@lists.linux.dev hch@lst.de jack@suse.com jack@suse.cz jfs-discussion@lists.sourceforge.net kmehltretter@gmail.com konishi.ryusuke@gmail.com linux-btrfs@vger.kernel.org linux-efi@vger.kernel.org linux-ext4@vger.kernel.org linux-fsdevel@vger.kernel.org linux-mm@kvack.org linux-mtd@lists.infradead.org linux-nilfs@vger.kernel.org linux-xfs@vger.kernel.org ntfs@lists.linux.dev ocfs2-devel@lists.linux.dev slava@dubeyko.com stable@vger.kernel.org viro@zeniv.linux.org.uk

Name	Content [All]
[PATCH v2 01/34] ecryptfs: don't leak the inode when a lookup can't open the lower file	[Body]
[PATCH v2 02/34] ecryptfs: fall back to a read-only lower file	[Body]
[PATCH v2 03/34] fs: add a generic emergency read-only state	[Body]
[PATCH v2 04/34] ext2: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v2 05/34] jfs: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v2 06/34] nilfs2: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v2 07/34] fat: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v2 08/34] exfat: keep the current mount options on remount	[Body]
[PATCH v2 09/34] exfat: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v2 10/34] exfat: use the generic emergency read-only state	[Body]
[PATCH v2 11/34] hfs: don't set SB_RDONLY after MDB write errors	[Body]
[PATCH v2 12/34] hfs: use the generic emergency read-only state	[Body]
[PATCH v2 13/34] hfsplus: don't set SB_RDONLY when creating the attributes tree	[Body]
[PATCH v2 14/34] affs: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v2 15/34] ufs: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v2 16/34] hpfs: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v2 17/34] ntfs: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v2 18/34] ntfs: use the generic emergency read-only state	[Body]
[PATCH v2 19/34] ocfs2: keep the current mount options on remount	[Body]
[PATCH v2 20/34] ocfs2: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v2 21/34] zonefs: don't set SB_RDONLY after I/O errors	[Body]
[PATCH v2 22/34] zonefs: use the generic emergency read-only state	[Body]
[PATCH v2 23/34] btrfs: check BTRFS_FS_STATE_RO instead of SB_RDONLY at runtime	[Body]
[PATCH v2 24/34] btrfs: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v2 25/34] gfs2: wait for a pending withdraw before remounting read-only	[Body]
[PATCH v2 26/34] gfs2: don't set SB_RDONLY on withdraw	[Body]
[PATCH v2 27/34] efivarfs: stop using SB_RDONLY for read-only efivar ops	[Body]
[PATCH v2 28/34] ubifs: don't set SB_RDONLY after errors	[Body]
[PATCH v2 29/34] selftests/filesystems: test filesystem errors while frozen	[Body]
[PATCH v2 30/34] ext4: allow remounting read-only in the emergency state	[Body]
[PATCH v2 31/34] ext4: use the generic emergency read-only state	[Body]
[PATCH v2 32/34] selftests/filesystems: test ext4 remounts in the emergency state	[Body]
[PATCH v2 33/34] xfs: allow remounting read-only after a shutdown	[Body]
[PATCH v2 34/34] selftests/filesystems: test xfs remounts after a shutdown	[Body]

Session 2026-10-29

waiting

ID (for dev)	1b9bf899-b2cf-4237-ad3d-92c7e526c750
Status	waiting

Test	Base	Patched	Verdict

Patches (34)

Series Summary

Sessions

Session 2026-10-29