From: John Fastabend <john.fastabend@gmail.com>
To: Eric Biggers <ebiggers@kernel.org>,
John Fastabend <john.fastabend@gmail.com>
Cc: syzbot <syzbot+8893700724999566d6a9@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, ast@kernel.org, cai@lca.pw,
crecklin@redhat.com, daniel@iogearbox.net, keescook@chromium.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: slab-out-of-bounds Write in validate_chain
Date: Wed, 26 Jun 2019 15:24:58 -0700 [thread overview]
Message-ID: <5d13f0ba3d1aa_25912acd0de805bcce@john-XPS-13-9370.notmuch> (raw)
In-Reply-To: <20190625234808.GB116876@gmail.com>
Eric Biggers wrote:
> Hi John,
>
> On Tue, Jun 25, 2019 at 04:07:00PM -0700, syzbot wrote:
> > syzbot has bisected this bug to:
> >
> > commit e9db4ef6bf4ca9894bb324c76e01b8f1a16b2650
> > Author: John Fastabend <john.fastabend@gmail.com>
> > Date: Sat Jun 30 13:17:47 2018 +0000
> >
> > bpf: sockhash fix omitted bucket lock in sock_close
> >
>
> Are you working on this? This is the 6th open syzbot report that has been
> bisected to this commit, and I suspect it's the cause of many of the other
> 30 open syzbot reports I assigned to the bpf subsystem too
> (https://lore.kernel.org/bpf/20190624050114.GA30702@sol.localdomain/).
>
> Also, this is happening in mainline (v5.2-rc6).
>
> - Eric
Should have a fix today. It seems syzbot has found this bug repeatedly.
.John
prev parent reply other threads:[~2019-06-26 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000e672c6058bd7ee45@google.com>
2019-06-25 23:07 ` KASAN: slab-out-of-bounds Write in validate_chain syzbot
2019-06-25 23:48 ` Eric Biggers
2019-06-26 22:24 ` John Fastabend [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=5d13f0ba3d1aa_25912acd0de805bcce@john-XPS-13-9370.notmuch \
--to=john.fastabend@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cai@lca.pw \
--cc=crecklin@redhat.com \
--cc=daniel@iogearbox.net \
--cc=ebiggers@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+8893700724999566d6a9@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).