From: Dmitry Vyukov <dvyukov@google.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: Roland Dreier <roland@purestorage.com>,
linux-rdma@vger.kernel.org, Doug Ledford <dledford@redhat.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
rds-devel@oss.oracle.com,
syzbot <syzbot+db1c219466daac1083df@syzkaller.appspotmail.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: KASAN: use-after-free Read in __list_add_valid (5)
Date: Wed, 20 Feb 2019 16:42:47 +0100 [thread overview]
Message-ID: <CACT4Y+bm_nO=+Jzwr=d0j1u9F59BJB9fu8_5pY9n5ia4fU+y+A@mail.gmail.com> (raw)
In-Reply-To: <20180704232629.GJ725@sol.localdomain>
On Thu, Jul 5, 2018 at 1:26 AM Eric Biggers <ebiggers3@gmail.com> wrote:
>
> On Tue, May 15, 2018 at 01:49:23PM -0700, Roland Dreier wrote:
> > > Still reproducible on Linus' tree (commit 66e1c94db3cd4e) and on linux-next
> > > (next-20180511). Here's a simplified reproducer:
> >
> > Thanks! That's a fantastic test case.
> >
> > The issue is a race where rdma_listen() sees invalid state in the
> > middle of an rdma_bind_addr() call that will ultimately fail. I'll
> > send a proposed patch shortly.
> >
> > - R.
>
> Ping; there's still no fix merged for this. The reproducer also works as an
> unprivileged user.
I don't see any patch similar to the tested one being merged. But this
stopped happening, so let's do:
#syz fix: ucma: fix a use-after-free in ucma_resolve_ip()
prev parent reply other threads:[~2019-02-20 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 0:01 KASAN: use-after-free Read in __list_add_valid (5) syzbot
2018-05-13 23:02 ` Eric Biggers
2018-05-15 20:49 ` Roland Dreier
2018-07-04 23:26 ` Eric Biggers
2019-02-20 15:42 ` Dmitry Vyukov [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='CACT4Y+bm_nO=+Jzwr=d0j1u9F59BJB9fu8_5pY9n5ia4fU+y+A@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=dledford@redhat.com \
--cc=ebiggers3@gmail.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=roland@purestorage.com \
--cc=syzbot+db1c219466daac1083df@syzkaller.appspotmail.com \
--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).