Linux NILFS development
 help / color / mirror / Atom feed
 messages from 2026-10-12 10:21:31 to 2026-10-13 19:39:12 UTC [more...]

[PATCH RFC 00/28] fs: don't set SB_RDONLY after filesystem errors
 2026-10-13 19:39 UTC  (34+ messages)
` [PATCH RFC 04/28] jfs: "
` [PATCH RFC 05/28] nilfs2: "
` [PATCH RFC 06/28] fat: "
` [PATCH RFC 07/28] exfat: keep the current mount options on remount
` [PATCH RFC 08/28] exfat: don't set SB_RDONLY after filesystem errors
` [PATCH RFC 09/28] hfs: don't set SB_RDONLY after MDB write errors
  ` [Jfs-discussion] "
` [PATCH RFC 10/28] hfsplus: don't set SB_RDONLY when creating the attributes tree
  ` [Jfs-discussion] "
` [PATCH RFC 11/28] affs: don't set SB_RDONLY after filesystem errors
` [PATCH RFC 12/28] ufs: "
` [PATCH RFC 13/28] hpfs: "
` [PATCH RFC 14/28] ntfs: "
` [PATCH RFC 15/28] ocfs2: keep options that can't change on remount
` [PATCH RFC 16/28] ocfs2: don't set SB_RDONLY after filesystem errors
` [PATCH RFC 17/28] zonefs: don't set SB_RDONLY after I/O errors
` [PATCH RFC 18/28] btrfs: check BTRFS_FS_STATE_RO instead of SB_RDONLY at runtime
` [PATCH RFC 19/28] btrfs: don't set SB_RDONLY after filesystem errors
` [PATCH RFC 20/28] gfs2: wait for a pending withdraw before remounting read-only
` [PATCH RFC 21/28] gfs2: don't set SB_RDONLY on withdraw
` [PATCH RFC 22/28] efivarfs: stop using SB_RDONLY for read-only efivar ops
` [PATCH RFC 23/28] ubifs: don't set SB_RDONLY after errors
` [PATCH RFC 24/28] selftests/filesystems: test filesystem errors while frozen
` [PATCH RFC 25/28] ext4: allow remounting read-only in the emergency state
` [PATCH RFC 26/28] selftests/filesystems: test ext4 remounts "
` [PATCH RFC 27/28] xfs: allow remounting read-only after a shutdown
` [PATCH RFC 28/28] selftests/filesystems: test xfs remounts "


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox