Syzbot CI

Subject	fs: don't set SB_RDONLY after filesystem errors
Author	brauner@kernel.org
Date	2026-11-13 11:58:57 +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 hyc.lee@gmail.com jack@suse.com jack@suse.cz jfs-discussion@lists.sourceforge.net joseph.qi@linux.alibaba.com 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 v3 01/33] jfs: free uncommitted anonymous tlocks when evicting an inode	[Body]
[PATCH v3 02/33] jfs: use jfs_symlink_inode_operations in jfs_iget()	[Body]
[PATCH v3 03/33] ecryptfs: don't leak the inode when a lookup can't open the lower file	[Body]
[PATCH v3 04/33] ecryptfs: fall back to a read-only lower file	[Body]
[PATCH v3 05/33] fs: add a generic emergency read-only state	[Body]
[PATCH v3 06/33] ext2: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v3 07/33] jfs: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v3 08/33] nilfs2: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v3 09/33] fat: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v3 10/33] exfat: keep the current mount options on remount	[Body]
[PATCH v3 11/33] exfat: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v3 12/33] exfat: use the generic emergency read-only state	[Body]
[PATCH v3 13/33] hfs: don't set SB_RDONLY after MDB write errors	[Body]
[PATCH v3 14/33] hfs: use the generic emergency read-only state	[Body]
[PATCH v3 15/33] hfsplus: don't set SB_RDONLY when creating the attributes tree	[Body]
[PATCH v3 16/33] affs: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v3 17/33] ufs: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v3 18/33] hpfs: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v3 19/33] ntfs: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v3 20/33] ntfs: use the generic emergency read-only state	[Body]
[PATCH v3 21/33] ocfs2: keep the current mount options on remount	[Body]
[PATCH v3 22/33] ocfs2: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v3 23/33] zonefs: don't set SB_RDONLY after I/O errors	[Body]
[PATCH v3 24/33] zonefs: use the generic emergency read-only state	[Body]
[PATCH v3 25/33] btrfs: check BTRFS_FS_STATE_RO instead of SB_RDONLY at runtime	[Body]
[PATCH v3 26/33] btrfs: don't set SB_RDONLY after filesystem errors	[Body]
[PATCH v3 27/33] gfs2: wait for a pending withdraw before remounting read-only	[Body]
[PATCH v3 28/33] gfs2: don't set SB_RDONLY on withdraw	[Body]
[PATCH v3 29/33] efivarfs: stop using SB_RDONLY for read-only efivar ops	[Body]
[PATCH v3 30/33] ubifs: don't set SB_RDONLY after errors	[Body]
[PATCH v3 31/33] ext4: allow remounting read-only in the emergency state	[Body]
[PATCH v3 32/33] ext4: use the generic emergency read-only state	[Body]
[PATCH v3 33/33] xfs: allow remounting read-only after a shutdown	[Body]

Session 2026-11-13

waiting

ID (for dev)	74adcdd0-6c86-4e5d-8655-3e8d8c8c42bc
Status	waiting

Test	Base	Patched	Verdict

Patches (33)

Series Summary

Sessions

Session 2026-11-13