From: syzbot <syzbot+0dd5b81275fa083055d7@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, brauner@kernel.org,
clang-built-linux@googlegroups.com, harshadshirwadkar@gmail.com,
jack@suse.cz, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, nathan@kernel.org,
ndesaulniers@google.com, syzkaller-bugs@googlegroups.com,
tytso@mit.edu
Subject: Re: [syzbot] [ext4?] INFO: task hung in ext4_stop_mmpd
Date: Mon, 21 Oct 2024 16:37:04 -0700 [thread overview]
Message-ID: <6716e5a0.050a0220.10f4f4.00d2.GAE@google.com> (raw)
In-Reply-To: <000000000000690606061ce1fe7e@google.com>
syzbot suspects this issue was fixed by commit:
commit d3476f3dad4ad68ae5f6b008ea6591d1520da5d8
Author: Jan Kara <jack@suse.cz>
Date: Mon Aug 5 20:12:41 2024 +0000
ext4: don't set SB_RDONLY after filesystem errors
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10d04640580000
start commit: 4a39ac5b7d62 Merge tag 'random-6.12-rc1-for-linus' of git:..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=dd14c10ec1b6af25
dashboard link: https://syzkaller.appspot.com/bug?extid=0dd5b81275fa083055d7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14fbd177980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=108ea607980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: ext4: don't set SB_RDONLY after filesystem errors
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-10-21 23:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 10:20 [syzbot] [ext4?] INFO: task hung in ext4_stop_mmpd syzbot
2024-09-19 8:31 ` syzbot
2024-09-20 19:06 ` syzbot
2024-10-21 23:37 ` syzbot [this message]
2024-10-22 9:03 ` 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=6716e5a0.050a0220.10f4f4.00d2.GAE@google.com \
--to=syzbot+0dd5b81275fa083055d7@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=brauner@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=harshadshirwadkar@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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