From: syzbot <syzbot+db0c9917f71539bc4ad1@syzkaller.appspotmail.com>
To: axboe@kernel.dk, cs.temp3@bpchargemaster.com, hdanton@sina.com,
josef@toxicpanda.com, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mail@anirudhrb.com, nbd@other.debian.org,
nsd-public@police.gov.hk, stephen.s.brennan@oracle.com,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] general protection fault in nbd_disconnect_and_put
Date: Wed, 22 Sep 2021 09:11:07 -0700 [thread overview]
Message-ID: <000000000000050d0d05cc97c35f@google.com> (raw)
In-Reply-To: <000000000000e692c905bbe9192c@google.com>
syzbot suspects this issue was fixed by commit:
commit 794ebcea865bff47231de89269e9d542121ab7be
Author: Stephen Brennan <stephen.s.brennan@oracle.com>
Date: Wed Sep 1 17:51:42 2021 +0000
namei: Standardize callers of filename_lookup()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1163691d300000
start commit: acd3d2859453 Merge tag 'fixes-v5.13' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f04bb30bd3c55050
dashboard link: https://syzkaller.appspot.com/bug?extid=db0c9917f71539bc4ad1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13f63543d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=122c8ef1d00000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: namei: Standardize callers of filename_lookup()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-09-22 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 9:05 general protection fault in nbd_disconnect_and_put syzbot
2021-09-22 16:11 ` 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=000000000000050d0d05cc97c35f@google.com \
--to=syzbot+db0c9917f71539bc4ad1@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=cs.temp3@bpchargemaster.com \
--cc=hdanton@sina.com \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@anirudhrb.com \
--cc=nbd@other.debian.org \
--cc=nsd-public@police.gov.hk \
--cc=stephen.s.brennan@oracle.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.