From: Gabriel Shahrouzi <gshahrouzi@gmail.com>
To: syzbot <syzbot+aec9606169fbc3a12ca6@syzkaller.appspotmail.com>
Cc: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
charmitro@posteo.net, skhan@linuxfoundation.org,
kernelmentees@lists.linuxfoundation.org,
Gabriel Shahrouzi <gshahrouzi@gmail.com>
Subject: [PATCH] bcache: Prevent granting write refs when filesystem is read-only
Date: Sat, 12 Apr 2025 14:39:33 -0400 [thread overview]
Message-ID: <20250412183933.252062-1-gshahrouzi@gmail.com> (raw)
Fix a shutdown WARNING in bch2_dev_free caused by active write I/O
references (ca->io_ref[WRITE]) on a device being freed.
The problem occurs when:
- The filesystem is marked read-only (BCH_FS_rw clear in c->flags).
- A subsequent operation (e.g., error handling for device removal)
incorrectly tries to grant write references back to a device.
- During final shutdown, the read-only flag causes the system to skip
stopping write I/O references (bch2_dev_io_ref_stop(ca, WRITE)).
- The leftover active write reference triggers the WARN_ON in
bch2_dev_free.
Prevent this by checking if the filesystem is read-only before
attempting to grant write references to a device in the problematic
code path. Ensure consistency between the filesystem state flag
and the device I/O reference state during shutdown.
---
Not sure what to put for the fixes tag so I omitted it. The bisection
that Syzkaller found technically is correct but only because additional
warn_on checks were added recently. The git blame shows code from 8
years ago for the specific lines being modified.
Also not sure if devices should have read and write permissions
(ca->mi.state = BCH_MEMBER_STATE_rw) when filesystem is in read-only
mode. If that is what intended, then I believe this solution works.There
could potentially be other places where a similar scenario occurs.
Reported-by: syzbot+aec9606169fbc3a12ca6@syzkaller.appspotmail.com
Closes: https://lore.kernel.org/all/67f50e3e.050a0220.396535.0560.GAE@google.com/T/
Signed-off-by: Gabriel Shahrouzi <gshahrouzi@gmail.com>
---
fs/bcachefs/super.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/bcachefs/super.c b/fs/bcachefs/super.c
index b79e80a435e09..788e870bfef6a 100644
--- a/fs/bcachefs/super.c
+++ b/fs/bcachefs/super.c
@@ -1757,7 +1757,8 @@ int bch2_dev_remove(struct bch_fs *c, struct bch_dev *ca, int flags)
up_write(&c->state_lock);
return 0;
err:
- if (ca->mi.state == BCH_MEMBER_STATE_rw &&
+ if (test_bit(BCH_FS_rw, &c->flags) &&
+ ca->mi.state == BCH_MEMBER_STATE_rw &&
!percpu_ref_is_zero(&ca->io_ref[READ]))
__bch2_dev_read_write(c, ca);
up_write(&c->state_lock);
--
2.43.0
next reply other threads:[~2025-04-12 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-12 18:39 Gabriel Shahrouzi [this message]
2025-04-13 9:56 ` Kent Overstreet
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=20250412183933.252062-1-gshahrouzi@gmail.com \
--to=gshahrouzi@gmail.com \
--cc=charmitro@posteo.net \
--cc=kent.overstreet@linux.dev \
--cc=kernelmentees@lists.linuxfoundation.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+aec9606169fbc3a12ca6@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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
Powered by JetHome