From: syzbot <syzbot+aa7397130ec6a8c2e2d9@syzkaller.appspotmail.com>
To: axboe@kernel.dk, boqun.feng@gmail.com, brauner@kernel.org,
dvyukov@google.com, hdanton@sina.com, jack@suse.com,
jack@suse.cz, jfs-discussion@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
penguin-kernel@i-love.sakura.ne.jp,
reiserfs-devel@vger.kernel.org, shaggy@kernel.org,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org
Subject: Re: [syzbot] [reiserfs?] INFO: task hung in deactivate_super (2)
Date: Tue, 02 Apr 2024 05:53:02 -0700 [thread overview]
Message-ID: <0000000000001ea9dc06151c9630@google.com> (raw)
In-Reply-To: <00000000000082de1c05f81467ed@google.com>
syzbot suspects this issue was fixed by commit:
commit 6f861765464f43a71462d52026fbddfc858239a5
Author: Jan Kara <jack@suse.cz>
Date: Wed Nov 1 17:43:10 2023 +0000
fs: Block writes to mounted block devices
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16799ab5180000
start commit: ac865f00af29 Merge tag 'pci-v6.7-fixes-2' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=655f8abe9fe69b3b
dashboard link: https://syzkaller.appspot.com/bug?extid=aa7397130ec6a8c2e2d9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1669644de80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=137d7db5e80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs: Block writes to mounted block devices
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-04-02 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000082de1c05f81467ed@google.com>
2024-01-04 11:28 ` [syzbot] [reiserfs?] INFO: task hung in deactivate_super (2) syzbot
2024-04-02 12:53 ` syzbot [this message]
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=0000000000001ea9dc06151c9630@google.com \
--to=syzbot+aa7397130ec6a8c2e2d9@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=dvyukov@google.com \
--cc=hdanton@sina.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=reiserfs-devel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).