From: syzbot <syzbot+cdfcae656bac88ba0e2d@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, konishi.ryusuke@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nilfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nilfs?] WARNING in mark_buffer_dirty (5)
Date: Thu, 17 Aug 2023 17:58:23 -0700 [thread overview]
Message-ID: <0000000000009095e80603280632@google.com> (raw)
In-Reply-To: <0000000000003da75f05fdeffd12@google.com>
syzbot has bisected this issue to:
commit 28a65b49eb53e172d23567005465019658bfdb4d
Author: Ryusuke Konishi <konishi.ryusuke@gmail.com>
Date: Thu Apr 27 01:15:26 2023 +0000
nilfs2: do not write dirty data after degenerating to read-only
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11c5be4ba80000
start commit: 6eaae1980760 Linux 6.5-rc3
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=13c5be4ba80000
console output: https://syzkaller.appspot.com/x/log.txt?x=15c5be4ba80000
kernel config: https://syzkaller.appspot.com/x/.config?x=5d10d93e1ae1f229
dashboard link: https://syzkaller.appspot.com/bug?extid=cdfcae656bac88ba0e2d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=127ac14ea80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1693a06ea80000
Reported-by: syzbot+cdfcae656bac88ba0e2d@syzkaller.appspotmail.com
Fixes: 28a65b49eb53 ("nilfs2: do not write dirty data after degenerating to read-only")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-18 0:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 15:01 [syzbot] [nilfs?] WARNING in mark_buffer_dirty (5) syzbot
2023-08-18 0:58 ` syzbot [this message]
2023-08-18 13:18 ` [PATCH] nilfs2: fix WARNING in mark_buffer_dirty due to discarded buffer reuse Ryusuke Konishi
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=0000000000009095e80603280632@google.com \
--to=syzbot+cdfcae656bac88ba0e2d@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).