From: syzbot <syzbot+7078ae989d857fe17988@syzkaller.appspotmail.com>
To: anmol.karan123@gmail.com, davem@davemloft.net, kuba@kernel.org,
linux-hams@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, ralf@linux-mips.org,
syzkaller-bugs@googlegroups.com, yepeilin.cs@gmail.com
Subject: Re: general protection fault in rose_send_frame
Date: Sun, 20 Dec 2020 05:27:03 -0800 [thread overview]
Message-ID: <00000000000014086305b6e54cfc@google.com> (raw)
In-Reply-To: <00000000000089904d057f1e0ae0@google.com>
syzbot suspects this issue was fixed by commit:
commit 3b3fd068c56e3fbea30090859216a368398e39bf
Author: Anmol Karn <anmol.karan123@gmail.com>
Date: Thu Nov 19 19:10:43 2020 +0000
rose: Fix Null pointer dereference in rose_send_frame()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=139e2b9b500000
start commit: 23ee3e4e Merge tag 'pci-v5.8-fixes-2' of git://git.kernel...
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f87a5e4232fdb267
dashboard link: https://syzkaller.appspot.com/bug?extid=7078ae989d857fe17988
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=157e8964900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10046c54900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: rose: Fix Null pointer dereference in rose_send_frame()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-12-20 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 17:38 general protection fault in rose_send_frame syzbot
2019-02-04 5:43 ` syzbot
2019-02-22 18:26 ` syzbot
2019-03-21 17:39 ` syzbot
2020-12-20 13:27 ` syzbot [this message]
2020-12-21 9:22 ` 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=00000000000014086305b6e54cfc@google.com \
--to=syzbot+7078ae989d857fe17988@syzkaller.appspotmail.com \
--cc=anmol.karan123@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yepeilin.cs@gmail.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 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.