From: syzbot <syzbot+c9db9ae0bd780a3094e1@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, chenzhongjin@huawei.com,
konishi.ryusuke@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] general protection fault in end_page_writeback
Date: Thu, 26 Jan 2023 22:06:26 -0800 [thread overview]
Message-ID: <000000000000690e9405f338aa34@google.com> (raw)
In-Reply-To: <0000000000002f9ede05eb40cfbd@google.com>
syzbot suspects this issue was fixed by commit:
commit 512c5ca01a3610ab14ff6309db363de51f1c13a6
Author: Chen Zhongjin <chenzhongjin@huawei.com>
Date: Fri Nov 18 06:33:04 2022 +0000
nilfs2: fix nilfs_sufile_mark_dirty() not set segment usage as dirty
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=138e4485480000
start commit: 55be6084c8e0 Merge tag 'timers-core-2022-10-05' of git://g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=df75278aabf0681a
dashboard link: https://syzkaller.appspot.com/bug?extid=c9db9ae0bd780a3094e1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11ad8cc2880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=106b5906880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: nilfs2: fix nilfs_sufile_mark_dirty() not set segment usage as dirty
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-01-27 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 20:27 [syzbot] general protection fault in end_page_writeback syzbot
2023-01-27 6:06 ` syzbot [this message]
2023-01-27 7:18 ` Dmitry Vyukov
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=000000000000690e9405f338aa34@google.com \
--to=syzbot+c9db9ae0bd780a3094e1@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=chenzhongjin@huawei.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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