From: Eric Biggers <ebiggers3@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: syzbot <syzbot+7a1cff37dbbef9e7ba4c@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, dhowells@redhat.com,
gs051095@gmail.com, linux-kernel@vger.kernel.org,
oleg@redhat.com, pasha.tatashin@oracle.com, riel@redhat.com,
rppt@linux.vnet.ibm.com, syzkaller-bugs@googlegroups.com,
wangkefeng.wang@huawei.com
Subject: Re: KASAN: use-after-free Read in alloc_pid
Date: Mon, 2 Apr 2018 20:10:21 -0700 [thread overview]
Message-ID: <20180403031021.GB685@sol.localdomain> (raw)
In-Reply-To: <878ta5z00m.fsf@xmission.com>
On Mon, Apr 02, 2018 at 06:00:57PM -0500, Eric W. Biederman wrote:
> syzbot <syzbot+7a1cff37dbbef9e7ba4c@syzkaller.appspotmail.com> writes:
>
> > Hello,
> >
> > syzbot hit the following crash on upstream commit
> > 9dd2326890d89a5179967c947dab2bab34d7ddee (Fri Mar 30 17:29:47 2018 +0000)
> > Merge tag 'ceph-for-4.16-rc8' of git://github.com/ceph/ceph-client
> > syzbot dashboard link:
> > https://syzkaller.appspot.com/bug?extid=7a1cff37dbbef9e7ba4c
> >
> > So far this crash happened 4 times on upstream.
> >
> > Unfortunately, I don't have any reproducer for this crash yet.
>
> Do you have any of the other traces? This looks like a something is
> calling put_pid_ns more than it is calling get_pid_ns causing a
> reference count mismatch.
>
> If this is not: 9ee332d99e4d5a97548943b81c54668450ce641b
>
> I could use a few more hints to help narrow down what is going wrong.
>
> It would be nice to know what the other 3 crashes looked like and
> exactly which upstream they were on.
>
The other crashes are shown on the syzbot dashboard (link was given in the
original email).
Eric
next prev parent reply other threads:[~2018-04-03 3:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 8:21 syzbot
2018-04-02 23:00 ` Eric W. Biederman
2018-04-03 3:10 ` Eric Biggers [this message]
2018-04-03 10:45 ` Tetsuo Handa
2018-04-10 14:11 ` syzbot
2018-04-10 14:33 ` Tetsuo Handa
2018-04-21 10:43 ` Tetsuo Handa
2018-04-24 16:33 ` Eric W. Biederman
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=20180403031021.GB685@sol.localdomain \
--to=ebiggers3@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=gs051095@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pasha.tatashin@oracle.com \
--cc=riel@redhat.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=syzbot+7a1cff37dbbef9e7ba4c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wangkefeng.wang@huawei.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®