From: Jason Gunthorpe <jgg@mellanox.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: syzbot <syzbot+e11efb687f5ab7f01f3d@syzkaller.appspotmail.com>,
dledford@redhat.com, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, monis@mellanox.com,
syzkaller-bugs@googlegroups.com, yanjunz@mellanox.com
Subject: Re: KASAN: use-after-free Read in rxe_query_port
Date: Tue, 10 Mar 2020 11:52:20 -0300 [thread overview]
Message-ID: <20200310145220.GO13183@mellanox.com> (raw)
In-Reply-To: <20200310073936.GF172334@unreal>
On Tue, Mar 10, 2020 at 09:39:36AM +0200, Leon Romanovsky wrote:
> On Mon, Mar 09, 2020 at 02:34:51PM -0300, Jason Gunthorpe wrote:
> > On Sun, Mar 01, 2020 at 03:20:12AM -0800, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit: f8788d86 Linux 5.6-rc3
> > > git tree: upstream
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=132d3645e00000
> > > kernel config: https://syzkaller.appspot.com/x/.config?x=9833e26bab355358
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=e11efb687f5ab7f01f3d
> > > compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> > >
> > > Unfortunately, I don't have any reproducer for this crash yet.
> > >
> > > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > > Reported-by: syzbot+e11efb687f5ab7f01f3d@syzkaller.appspotmail.com
> >
> > Yanjun, do you have some idea what this could be?
>
> See this fix in the net mailing list.
> https://lore.kernel.org/netdev/20200306134518.84416-1-kgraul@linux.ibm.com
Yes, seems right to me, that work is calling ib_query_port().
#syz dup: WARNING: ODEBUG bug in smc_ib_remove_dev
Jason
prev parent reply other threads:[~2020-03-10 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 11:20 syzbot
2020-03-09 17:34 ` Jason Gunthorpe
2020-03-10 2:43 ` Yanjun Zhu
2020-03-10 7:39 ` Leon Romanovsky
2020-03-10 8:21 ` Yanjun Zhu
2020-03-10 8:41 ` Leon Romanovsky
2020-03-10 14:52 ` Jason Gunthorpe [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=20200310145220.GO13183@mellanox.com \
--to=jgg@mellanox.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=monis@mellanox.com \
--cc=syzbot+e11efb687f5ab7f01f3d@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yanjunz@mellanox.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®