From: santosh.shilimkar@oracle.com
To: Cong Wang <xiyou.wangcong@gmail.com>,
syzbot <syzbot+fae39afd2101a17ec624@syzkaller.appspotmail.com>
Cc: Arvid Brodin <arvid.brodin@alten.se>,
David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
linux-rdma@vger.kernel.org,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
rds-devel@oss.oracle.com,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in rds_bind
Date: Mon, 16 Sep 2019 10:57:30 -0700 [thread overview]
Message-ID: <d64dee71-4927-4589-d865-7abf4cc266e6@oracle.com> (raw)
In-Reply-To: <CAM_iQpXdTNVywYm6+vmAKMsBRcC6ySOX9Rcg70xhgdjJgbDJkw@mail.gmail.com>
On 9/16/19 9:49 AM, Cong Wang wrote:
> On Mon, Sep 16, 2019 at 6:29 AM syzbot
> <syzbot+fae39afd2101a17ec624@syzkaller.appspotmail.com> wrote:
>>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit: f4b752a6 mlx4: fix spelling mistake "veify" -> "verify"
>> git tree: net
>> console output: https://syzkaller.appspot.com/x/log.txt?x=16cbebe6600000
>> kernel config: https://syzkaller.appspot.com/x/.config?x=b89bb446a3faaba4
>> dashboard link: https://syzkaller.appspot.com/bug?extid=fae39afd2101a17ec624
>> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10753bc1600000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=111dfc11600000
>>
>> The bug was bisected to:
>>
>> commit b9a1e627405d68d475a3c1f35e685ccfb5bbe668
>> Author: Cong Wang <xiyou.wangcong@gmail.com>
>> Date: Thu Jul 4 00:21:13 2019 +0000
>>
>> hsr: implement dellink to clean up resources
>
>
> The crash has nothing to do with this commit. It is probably caused
> by the lack of ->laddr_check in rds_loop_transport.
>
Will have a look.
regards,
Santosh
prev parent reply other threads:[~2019-09-16 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 13:29 syzbot
2019-09-16 16:49 ` Cong Wang
2019-09-16 17:57 ` santosh.shilimkar [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=d64dee71-4927-4589-d865-7abf4cc266e6@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=arvid.brodin@alten.se \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=syzbot+fae39afd2101a17ec624@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®