From: syzbot <syzbot+2da5e132dd0268a9c0e4@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, axboe@kernel.dk, bvanassche@acm.org,
idosch@nvidia.com, jack@suse.cz, jacob.e.keller@intel.com,
jiri@nvidia.com, jlayton@kernel.org, kuba@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
neilb@suse.de, pabeni@redhat.com, reiserfs-devel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, willy@infradead.org,
yi.zhang@huawei.com
Subject: Re: [syzbot] [reiserfs?] kernel BUG in do_journal_begin_r
Date: Tue, 21 Mar 2023 14:26:23 -0700 [thread overview]
Message-ID: <00000000000000f2d005f76fb25e@google.com> (raw)
In-Reply-To: <00000000000022a65705ec7f923c@google.com>
syzbot suspects this issue was fixed by commit:
commit b20b8aec6ffc07bb547966b356780cd344f20f5b
Author: Ido Schimmel <idosch@nvidia.com>
Date: Wed Feb 15 07:31:39 2023 +0000
devlink: Fix netdev notifier chain corruption
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=139af019c80000
start commit: 033c40a89f55 Merge tag 'apparmor-v6.2-rc9' of git://git.ke..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=fe56f7d193926860
dashboard link: https://syzkaller.appspot.com/bug?extid=2da5e132dd0268a9c0e4
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1264a8d7480000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: devlink: Fix netdev notifier chain corruption
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-03-21 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 16:45 [syzbot] kernel BUG in do_journal_begin_r syzbot
2022-11-21 9:51 ` syzbot
2022-11-21 22:57 ` syzbot
2023-03-21 21:26 ` 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=00000000000000f2d005f76fb25e@google.com \
--to=syzbot+2da5e132dd0268a9c0e4@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=idosch@nvidia.com \
--cc=jack@suse.cz \
--cc=jacob.e.keller@intel.com \
--cc=jiri@nvidia.com \
--cc=jlayton@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=pabeni@redhat.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
--cc=yi.zhang@huawei.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