From: syzbot <syzbot+adb15cf8c2798e4e0db4@syzkaller.appspotmail.com>
To: ebiggers@kernel.org, jgg@mellanox.com,
linux-rdma@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in rdma_listen (2)
Date: Tue, 18 Feb 2020 14:10:04 -0800 [thread overview]
Message-ID: <0000000000000ed37d059ee0efb4@google.com> (raw)
In-Reply-To: <20200218210432.GA31966@ziepe.ca>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger crash:
Reported-and-tested-by: syzbot+adb15cf8c2798e4e0db4@syzkaller.appspotmail.com
Tested on:
commit: 11a48a5a Linux 5.6-rc2
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git for-rc
kernel config: https://syzkaller.appspot.com/x/.config?x=3e5684f9a45838bb
dashboard link: https://syzkaller.appspot.com/bug?extid=adb15cf8c2798e4e0db4
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
patch: https://syzkaller.appspot.com/x/patch.diff?x=14709845e00000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2020-02-18 22:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 21:04 [PATCH] RDMA/ucma: Put a lock around every call to the rdma_cm layer Jason Gunthorpe
2020-02-18 22:10 ` syzbot [this message]
2020-02-19 6:07 ` Eric Biggers
2020-02-19 20:22 ` Jason Gunthorpe
2020-03-07 20:41 ` Eric Biggers
2020-03-09 19:30 ` Jason Gunthorpe
2020-06-27 22:57 ` Eric Biggers
2020-06-29 14:30 ` Jason Gunthorpe
2020-11-16 20:46 ` Jason Gunthorpe
2020-02-27 20:42 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2019-03-30 6:44 KASAN: use-after-free Read in rdma_listen (2) syzbot
2020-02-17 23:33 ` syzbot
[not found] ` <20200218122717.10748-1-hdanton@sina.com>
2020-02-18 19:13 ` Jason Gunthorpe
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=0000000000000ed37d059ee0efb4@google.com \
--to=syzbot+adb15cf8c2798e4e0db4@syzkaller.appspotmail.com \
--cc=ebiggers@kernel.org \
--cc=jgg@mellanox.com \
--cc=linux-rdma@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).