From: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
ecryptfs@vger.kernel.org, linux-ext4@vger.kernel.org,
jfs-discussion@lists.sourceforge.net,
linux-nilfs@vger.kernel.org, exfat@lists.linux.dev,
linux-fsdevel@vger.kernel.org, ntfs@lists.linux.dev,
ocfs2-devel@lists.linux.dev, linux-btrfs@vger.kernel.org,
gfs2@lists.linux.dev, linux-efi@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-xfs@vger.kernel.org,
"Christian Brauner (Amutable)" <brauner@kernel.org>,
stable@vger.kernel.org
Subject: [PATCH RFC 09/28] hfs: don't set SB_RDONLY after MDB write errors
Date: Mon, 12 Oct 2026 12:20:54 +0200 [thread overview]
Message-ID: <20261012-work-fs-sb_rdonly-v1-9-60743a3dc326@kernel.org> (raw)
In-Reply-To: <20261012-work-fs-sb_rdonly-v1-0-60743a3dc326@kernel.org>
Since commit fdbb95ff89b2 ("hfs: don't re-dirty MDB buffers after a
write failure") hfs_mdb_commit() sets SB_RDONLY when the MDB or the
alternate MDB buffer lost BH_Uptodate after a failed write.
hfs_mdb_commit() runs from the flush_mdb work without holding
sb->s_umount and from ->sync_fs(), e.g. for sync(2) which only holds
s_umount shared. Neither may change SB_RDONLY.
freeze_super() decides from sb_rdonly() whether to take the s_writers
rwsems and then drops s_umount while it waits for writers in
sb_wait_write(SB_FREEZE_WRITE). A sync(2) in that window gets to
hfs_mdb_commit() which flips SB_RDONLY. sync_filesystem() in
freeze_super() then returns early for the now read-only superblock, the
freeze completes with all three rwsems held and thaw_super() sees
sb_rdonly() and skips sb_freeze_unlock(). So the rwsems stay
write-locked on a superblock that is marked unfrozen. The commit from
sync(2) reports:
hfs: primary MDB is corrupt, mounting read-only
and after the thaw writers block forever and umount warns:
INFO: task s3_fsop:162 blocked for more than 30 seconds.
WARNING: kernel/rcu/sync.c:177 at rcu_sync_dtor+0x143/0x190
hfs has no ->freeze_fs() so this needs bdev_freeze(), e.g. through a
device mapper suspend with lockfs.
Follow what ext4 did in commit d3476f3dad4a ("ext4: don't set SB_RDONLY
after filesystem errors") and record the condition in a new
HFS_FLG_EMERGENCY_RO bit next to the MDB and bitmap dirty bits instead.
The bit is never cleared. The messages and the -EIO from the call that
detects the problem stay as they are. Later calls to hfs_mdb_commit()
return 0 early exactly like they did for sb_rdonly(), so syncs and
freezes keep working after the error. And the MDB is never marked
cleanly unmounted after the error.
hfs now refuses modifications with -EROFS itself. That's the namespace
operations, setattr, the hfs.type and hfs.creator xattrs, opening for
write, write_begin, O_DIRECT writes and block allocation for files in
hfs_get_block(). hfs_file_truncate() returns early too. It runs from
->release() on the last close and frees preallocated blocks without any
freeze protection.
Note that b-tree growth through hfs_bmap_reserve() isn't refused. A read
that needs another extent record first writes back the cached one. If
that record was created before the error inserting it can need a new
b-tree node and refusing that would make such reads fail with -EIO until
umount.
hfs_write_inode() refuses to write inodes back as well. Writeback clears
the dirty state of an inode before it calls ->write_inode() and doesn't
redirty it when that fails. So fsync() would happily report success for
an inode that never made it to disk. Let fsync() fail with -EROFS
instead. Like on ext4 an operation that completed shortly before the
error can end up half-applied on disk and needs fsck.hfs.
Only the headers of the extents and catalog b-trees are still written.
Writeback writes the b-tree nodes anyway and a node that gets allocated
after the error, e.g. by a read that writes back a cached extent
record, needs a header that knows about it. Otherwise the next mount
starts from a stale root and misses records.
A remount to read-write fails with -EROFS until umount and a remount to
read-only is allowed. Like ext4 we show "emergency_ro" in the mount
options. The mount stays "rw" and writes through file descriptors opened
before the error now fail with -EROFS.
Reproducer. The writer parked in sb_start_write() keeps freeze_super()
in sb_wait_write() with s_umount dropped while sync(2) runs:
hformat /dev/vdb; N=$(blockdev --getsz /dev/vdb)
dmsetup create h0 --table "0 $N linear /dev/vdb 0"
mount -t hfs /dev/mapper/h0 /mnt; echo a > /mnt/f; sync
printf '0 2 linear /dev/vdb 0\n2 1 error\n3 %d linear /dev/vdb 3\n' $((N-3)) |
dmsetup load h0 # fail writes to the MDB sector
dmsetup suspend --nolockfs h0; dmsetup resume h0
echo b > /mnt/h; sleep 6 # flush_mdb: MDB write fails, mdb_bh !uptodate
sync /mnt/f # fsync(): consumes the bdev mapping's AS_EIO
<writer: splice() from an empty pipe into /mnt/f> # parked in sb_start_write()
dmsetup suspend h0 & # freeze_super() waits for the writer
sync # hfs_mdb_commit(): "primary MDB is corrupt" -> SB_RDONLY
<feed the pipe> # freeze completes, sync_filesystem() skipped
dmsetup resume h0 # thaw_super() skips sb_freeze_unlock()
touch /mnt/x # hangs in sb_start_write()
Fixes: fdbb95ff89b2 ("hfs: don't re-dirty MDB buffers after a write failure")
Cc: stable@vger.kernel.org
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
---
fs/hfs/attr.c | 3 +++
fs/hfs/dir.c | 12 ++++++++++++
fs/hfs/extent.c | 5 +++++
fs/hfs/hfs_fs.h | 11 +++++++++++
fs/hfs/inode.c | 30 ++++++++++++++++++++++++++++++
fs/hfs/mdb.c | 18 ++++++++++++------
fs/hfs/super.c | 7 ++++++-
7 files changed, 79 insertions(+), 7 deletions(-)
diff --git a/fs/hfs/attr.c b/fs/hfs/attr.c
index f8395cdd1adf..d7f8353322c8 100644
--- a/fs/hfs/attr.c
+++ b/fs/hfs/attr.c
@@ -129,6 +129,9 @@ static int hfs_xattr_set(const struct xattr_handler *handler,
if (!value)
return -EOPNOTSUPP;
+ if (unlikely(hfs_emergency_ro(inode->i_sb)))
+ return -EROFS;
+
return __hfs_setxattr(inode, handler->flags, value, size, flags);
}
diff --git a/fs/hfs/dir.c b/fs/hfs/dir.c
index e1f1fb351464..e7ed6e829b77 100644
--- a/fs/hfs/dir.c
+++ b/fs/hfs/dir.c
@@ -189,6 +189,9 @@ static int hfs_create(struct mnt_idmap *idmap, struct inode *dir,
struct inode *inode;
int res;
+ if (unlikely(hfs_emergency_ro(dir->i_sb)))
+ return -EROFS;
+
inode = hfs_new_inode(dir, &dentry->d_name, mode);
if (IS_ERR(inode))
return PTR_ERR(inode);
@@ -219,6 +222,9 @@ static struct dentry *hfs_mkdir(struct mnt_idmap *idmap, struct inode *dir,
struct inode *inode;
int res;
+ if (unlikely(hfs_emergency_ro(dir->i_sb)))
+ return ERR_PTR(-EROFS);
+
inode = hfs_new_inode(dir, &dentry->d_name, mode);
if (IS_ERR(inode))
return ERR_CAST(inode);
@@ -252,6 +258,9 @@ static int hfs_remove(struct inode *dir, struct dentry *dentry)
struct inode *inode = d_inode(dentry);
int res;
+ if (unlikely(hfs_emergency_ro(sb)))
+ return -EROFS;
+
if (S_ISDIR(inode->i_mode) && inode->i_size != 2)
return -ENOTEMPTY;
@@ -290,6 +299,9 @@ static int hfs_rename(struct mnt_idmap *idmap, struct inode *old_dir,
if (flags & ~RENAME_NOREPLACE)
return -EINVAL;
+ if (unlikely(hfs_emergency_ro(old_dir->i_sb)))
+ return -EROFS;
+
/* Unlink destination if it already exists */
if (d_really_is_positive(new_dentry)) {
res = hfs_remove(new_dir, new_dentry);
diff --git a/fs/hfs/extent.c b/fs/hfs/extent.c
index f066a99a863b..dab31f159b1a 100644
--- a/fs/hfs/extent.c
+++ b/fs/hfs/extent.c
@@ -350,6 +350,9 @@ int hfs_get_block(struct inode *inode, sector_t block,
if (block > HFS_I(inode)->fs_blocks)
return -EIO;
if (ablock >= HFS_I(inode)->alloc_blocks) {
+ /* No new allocations after an error. */
+ if (unlikely(hfs_emergency_ro(sb)))
+ return -EROFS;
res = hfs_extend_file(inode);
if (res)
return res;
@@ -485,6 +488,8 @@ void hfs_file_truncate(struct inode *inode)
hfs_dbg("ino %llu, phys_size %llu -> i_size %llu\n",
inode->i_ino, (long long)HFS_I(inode)->phys_size,
inode->i_size);
+ if (unlikely(hfs_emergency_ro(sb)))
+ return;
if (inode->i_size > HFS_I(inode)->phys_size) {
struct address_space *mapping = inode->i_mapping;
void *fsdata = NULL;
diff --git a/fs/hfs/hfs_fs.h b/fs/hfs/hfs_fs.h
index e250f87a5e33..71ab81b649bc 100644
--- a/fs/hfs/hfs_fs.h
+++ b/fs/hfs/hfs_fs.h
@@ -143,6 +143,7 @@ struct hfs_sb_info {
#define HFS_FLG_BITMAP_DIRTY 0
#define HFS_FLG_MDB_DIRTY 1
#define HFS_FLG_ALT_MDB_DIRTY 2
+#define HFS_FLG_EMERGENCY_RO 3 /* read-only after an MDB write error */
/* bitmap.c */
extern u32 hfs_vbm_search_free(struct super_block *sb, u32 goal, u32 *num_bits);
@@ -293,6 +294,16 @@ static inline const char *hfs_mdb_name(struct super_block *sb)
return sb->s_id;
}
+/*
+ * Writing back the MDB failed and the filesystem stopped all modifications
+ * until unmount. SB_RDONLY isn't used for that because it must not change
+ * without s_umount.
+ */
+static inline bool hfs_emergency_ro(struct super_block *sb)
+{
+ return test_bit(HFS_FLG_EMERGENCY_RO, &HFS_SB(sb)->flags);
+}
+
static inline void hfs_bitmap_dirty(struct super_block *sb)
{
set_bit(HFS_FLG_BITMAP_DIRTY, &HFS_SB(sb)->flags);
diff --git a/fs/hfs/inode.c b/fs/hfs/inode.c
index 2aef3c36a150..42a2c2e390b2 100644
--- a/fs/hfs/inode.c
+++ b/fs/hfs/inode.c
@@ -54,6 +54,9 @@ int hfs_write_begin(const struct kiocb *iocb, struct address_space *mapping,
loff_t total_capacity;
int ret;
+ if (unlikely(hfs_emergency_ro(inode->i_sb)))
+ return -EROFS;
+
total_capacity = (loff_t)sbi->fs_ablocks * sbi->alloc_blksz;
if (pos >= total_capacity)
@@ -139,6 +142,10 @@ static ssize_t hfs_direct_IO(struct kiocb *iocb, struct iov_iter *iter)
size_t count = iov_iter_count(iter);
ssize_t ret;
+ if (iov_iter_rw(iter) == WRITE &&
+ unlikely(hfs_emergency_ro(inode->i_sb)))
+ return -EROFS;
+
ret = blockdev_direct_IO(iocb, inode, iter, hfs_get_block);
/*
@@ -472,6 +479,20 @@ int hfs_write_inode(struct inode *inode, struct writeback_control *wbc)
int res;
hfs_dbg("ino %llu\n", inode->i_ino);
+ if (unlikely(hfs_emergency_ro(inode->i_sb))) {
+ /*
+ * Writeback still writes the b-tree nodes. Keep the headers in
+ * sync with them so the trees on disk stay intact.
+ */
+ if (inode->i_ino == HFS_EXT_CNID)
+ hfs_btree_write(HFS_SB(inode->i_sb)->ext_tree);
+ else if (inode->i_ino == HFS_CAT_CNID)
+ hfs_btree_write(HFS_SB(inode->i_sb)->cat_tree);
+ else
+ return -EROFS;
+ return 0;
+ }
+
res = hfs_ext_write_extent(inode);
if (res)
return res;
@@ -619,6 +640,8 @@ void hfs_evict_inode(struct inode *inode)
static int hfs_file_open(struct inode *inode, struct file *file)
{
+ if ((file->f_mode & FMODE_WRITE) && hfs_emergency_ro(inode->i_sb))
+ return -EROFS;
if (HFS_IS_RSRC(inode))
inode = HFS_I(inode)->rsrc_inode;
atomic_inc(&HFS_I(inode)->opencnt);
@@ -650,6 +673,9 @@ int hfs_inode_setattr(struct mnt_idmap *idmap, struct dentry *dentry,
struct hfs_sb_info *hsb = HFS_SB(inode->i_sb);
int error;
+ if (unlikely(hfs_emergency_ro(inode->i_sb)))
+ return -EROFS;
+
error = setattr_prepare(&nop_mnt_idmap, dentry, attr);
if (error)
return error;
@@ -701,6 +727,10 @@ static int hfs_file_fsync(struct file *filp, loff_t start, loff_t end,
struct super_block * sb;
int ret, err;
+ /* Inodes aren't written back after an error. */
+ if (unlikely(hfs_emergency_ro(inode->i_sb)))
+ return -EROFS;
+
ret = file_write_and_wait_range(filp, start, end);
if (ret)
return ret;
diff --git a/fs/hfs/mdb.c b/fs/hfs/mdb.c
index 277de712f9d4..ce20824bbdc8 100644
--- a/fs/hfs/mdb.c
+++ b/fs/hfs/mdb.c
@@ -322,8 +322,8 @@ int hfs_mdb_get(struct super_block *sb)
* NONE
* Returns:
* 0 on success, -EIO if the MDB or alternate MDB buffer is no longer
- * valid (e.g. after a prior write error), in which case the volume is
- * remounted read-only.
+ * valid (e.g. after a prior write error), in which case the volume
+ * refuses all further modifications until it is unmounted.
* Preconditions:
* 'mdb' points to a "valid" (struct hfs_mdb).
* Postconditions:
@@ -338,12 +338,18 @@ int hfs_mdb_commit(struct super_block *sb)
struct hfs_mdb *mdb = HFS_SB(sb)->mdb;
int ret = 0;
- if (sb_rdonly(sb))
+ if (sb_rdonly(sb) || hfs_emergency_ro(sb))
return 0;
+ /*
+ * Don't set SB_RDONLY on errors: changing it requires s_umount and a
+ * remount. Setting it on a frozen superblock makes thaw_super() mark
+ * it unfrozen but skip sb_freeze_unlock(), so the s_writers rwsems
+ * stay write-locked and every writer hangs.
+ */
if (!buffer_uptodate(HFS_SB(sb)->mdb_bh)) {
pr_err("primary MDB is corrupt, mounting read-only\n");
- sb->s_flags |= SB_RDONLY;
+ set_bit(HFS_FLG_EMERGENCY_RO, &HFS_SB(sb)->flags);
return -EIO;
}
@@ -377,7 +383,7 @@ int hfs_mdb_commit(struct super_block *sb)
HFS_SB(sb)->alt_mdb) {
if (!buffer_uptodate(HFS_SB(sb)->alt_mdb_bh)) {
pr_err("alternate MDB is corrupt, mounting read-only\n");
- sb->s_flags |= SB_RDONLY;
+ set_bit(HFS_FLG_EMERGENCY_RO, &HFS_SB(sb)->flags);
ret = -EIO;
goto out;
}
@@ -428,7 +434,7 @@ int hfs_mdb_commit(struct super_block *sb)
void hfs_mdb_close(struct super_block *sb)
{
/* update volume attributes */
- if (sb_rdonly(sb))
+ if (sb_rdonly(sb) || hfs_emergency_ro(sb))
return;
if (!buffer_uptodate(HFS_SB(sb)->mdb_bh))
diff --git a/fs/hfs/super.c b/fs/hfs/super.c
index 5e6d66ff4bee..0f2c5ab0caf7 100644
--- a/fs/hfs/super.c
+++ b/fs/hfs/super.c
@@ -82,7 +82,7 @@ void hfs_mark_mdb_dirty(struct super_block *sb)
struct hfs_sb_info *sbi = HFS_SB(sb);
unsigned long delay;
- if (sb_rdonly(sb))
+ if (sb_rdonly(sb) || hfs_emergency_ro(sb))
return;
spin_lock(&sbi->work_lock);
@@ -131,6 +131,9 @@ static int hfs_reconfigure(struct fs_context *fc)
return 0;
if (!(fc->sb_flags & SB_RDONLY)) {
+ /* After an MDB write error it stays read-only until unmount. */
+ if (hfs_emergency_ro(sb))
+ return -EROFS;
if (!(HFS_SB(sb)->mdb->drAtrb & cpu_to_be16(HFS_SB_ATTRIB_UNMNT))) {
pr_warn("filesystem was not cleanly unmounted, running fsck.hfs is recommended. leaving read-only.\n");
sb->s_flags |= SB_RDONLY;
@@ -169,6 +172,8 @@ static int hfs_show_options(struct seq_file *seq, struct dentry *root)
seq_printf(seq, ",iocharset=%s", sbi->nls_io->charset);
if (sbi->s_quiet)
seq_printf(seq, ",quiet");
+ if (hfs_emergency_ro(root->d_sb))
+ seq_puts(seq, ",emergency_ro");
return 0;
}
--
2.53.0
next prev parent reply other threads:[~2026-10-12 10:21 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 10:20 [PATCH RFC 00/28] fs: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-10-12 10:20 ` [PATCH RFC 01/28] ecryptfs: don't leak the inode when a lookup can't open the lower file Christian Brauner
2026-10-12 10:34 ` sashiko-bot
2026-10-14 4:40 ` Tyler Hicks
2026-10-12 10:20 ` [PATCH RFC 02/28] ecryptfs: fall back to a read-only " Christian Brauner
2026-10-12 10:32 ` sashiko-bot
2026-10-12 10:20 ` [PATCH RFC 03/28] ext2: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-10-12 10:44 ` sashiko-bot
2026-10-12 10:20 ` [PATCH RFC 04/28] jfs: " Christian Brauner
2026-10-12 10:41 ` sashiko-bot
2026-10-12 10:20 ` [PATCH RFC 05/28] nilfs2: " Christian Brauner
2026-10-12 10:34 ` sashiko-bot
2026-10-13 16:01 ` Ryusuke Konishi
2026-10-12 10:20 ` [PATCH RFC 06/28] fat: " Christian Brauner
2026-10-12 10:37 ` sashiko-bot
2026-10-12 10:20 ` [PATCH RFC 07/28] exfat: keep the current mount options on remount Christian Brauner
2026-10-12 10:36 ` sashiko-bot
2026-10-12 10:20 ` [PATCH RFC 08/28] exfat: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-10-12 10:35 ` sashiko-bot
2026-10-12 10:20 ` Christian Brauner [this message]
2026-10-12 10:41 ` [PATCH RFC 09/28] hfs: don't set SB_RDONLY after MDB write errors sashiko-bot
2026-10-12 22:57 ` [Jfs-discussion] " Viacheslav Dubeyko
2026-10-12 10:20 ` [PATCH RFC 10/28] hfsplus: don't set SB_RDONLY when creating the attributes tree Christian Brauner
2026-10-12 10:36 ` sashiko-bot
2026-10-12 22:34 ` [Jfs-discussion] " Viacheslav Dubeyko
2026-10-12 10:20 ` [PATCH RFC 11/28] affs: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-10-12 10:41 ` sashiko-bot
2026-10-12 10:20 ` [PATCH RFC 12/28] ufs: " Christian Brauner
2026-10-12 10:39 ` sashiko-bot
2026-10-12 10:20 ` [PATCH RFC 13/28] hpfs: " Christian Brauner
2026-10-12 10:35 ` sashiko-bot
2026-10-12 10:20 ` [PATCH RFC 14/28] ntfs: " Christian Brauner
2026-10-12 10:45 ` sashiko-bot
2026-10-12 10:21 ` [PATCH RFC 15/28] ocfs2: keep options that can't change on remount Christian Brauner
2026-10-12 10:45 ` sashiko-bot
2026-10-12 10:21 ` [PATCH RFC 16/28] ocfs2: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-10-12 10:59 ` sashiko-bot
2026-10-12 10:21 ` [PATCH RFC 17/28] zonefs: don't set SB_RDONLY after I/O errors Christian Brauner
2026-10-12 10:42 ` sashiko-bot
2026-10-12 10:21 ` [PATCH RFC 18/28] btrfs: check BTRFS_FS_STATE_RO instead of SB_RDONLY at runtime Christian Brauner
2026-10-12 10:53 ` sashiko-bot
2026-10-12 10:21 ` [PATCH RFC 19/28] btrfs: don't set SB_RDONLY after filesystem errors Christian Brauner
2026-10-12 11:05 ` sashiko-bot
2026-10-12 10:21 ` [PATCH RFC 20/28] gfs2: wait for a pending withdraw before remounting read-only Christian Brauner
2026-10-12 10:44 ` sashiko-bot
2026-10-12 10:21 ` [PATCH RFC 21/28] gfs2: don't set SB_RDONLY on withdraw Christian Brauner
2026-10-12 10:48 ` sashiko-bot
2026-10-12 10:21 ` [PATCH RFC 22/28] efivarfs: stop using SB_RDONLY for read-only efivar ops Christian Brauner
2026-10-12 10:52 ` sashiko-bot
2026-10-12 10:21 ` [PATCH RFC 23/28] ubifs: don't set SB_RDONLY after errors Christian Brauner
2026-10-12 11:05 ` sashiko-bot
2026-10-12 10:21 ` [PATCH RFC 24/28] selftests/filesystems: test filesystem errors while frozen Christian Brauner
2026-10-12 10:47 ` sashiko-bot
2026-10-12 10:21 ` [PATCH RFC 25/28] ext4: allow remounting read-only in the emergency state Christian Brauner
2026-10-12 10:49 ` sashiko-bot
2026-10-12 16:38 ` Jan Kara
2026-10-12 10:21 ` [PATCH RFC 26/28] selftests/filesystems: test ext4 remounts " Christian Brauner
2026-10-12 10:52 ` sashiko-bot
2026-10-12 10:21 ` [PATCH RFC 27/28] xfs: allow remounting read-only after a shutdown Christian Brauner
2026-10-12 10:55 ` sashiko-bot
2026-10-13 7:38 ` Christoph Hellwig
2026-10-12 10:21 ` [PATCH RFC 28/28] selftests/filesystems: test xfs remounts " Christian Brauner
2026-10-12 10:51 ` sashiko-bot
2026-10-13 7:40 ` Christoph Hellwig
2026-10-12 16:53 ` [PATCH RFC 00/28] fs: don't set SB_RDONLY after filesystem errors Jan Kara
[not found] ` <20261013-forsten-ammoniak-geknackt-fefec366cc97@brauner>
2026-10-14 10:04 ` Andreas Gruenbacher
2026-10-14 13:47 ` Jan Kara
2026-10-14 13:41 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261012-work-fs-sb_rdonly-v1-9-60743a3dc326@kernel.org \
--to=brauner@kernel.org \
--cc=ecryptfs@vger.kernel.org \
--cc=exfat@lists.linux.dev \
--cc=gfs2@lists.linux.dev \
--cc=jack@suse.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ntfs@lists.linux.dev \
--cc=ocfs2-devel@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox