From: Aleksandr Nogikh <nogikh@google.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: syzbot <syzbot+48135e34de22e3a82c99@syzkaller.appspotmail.com>,
applications@thinkbigglobal.in,
David Miller <davem@davemloft.net>,
gustavo@padovan.org, Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Ingo Molnar <mingo@redhat.com>, Michal Marek <mmarek@suse.com>,
Netdev <netdev@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
Will Deacon <will@kernel.org>, Dmitry Vyukov <dvyukov@google.com>,
Aleksandr Nogikh <nogikh@google.com>
Subject: Re: [syzbot] KASAN: use-after-free Read in corrupted (4)
Date: Wed, 1 Jun 2022 13:51:20 +0000 [thread overview]
Message-ID: <Ypdu2H6fUOCZck1j@nogikh.google.com> (raw)
In-Reply-To: <CAHk-=whH5pmgyzE6+6C==p2VQFUgGiPhSwX=R2zKs+iHZuX7_A@mail.gmail.com>
Hi Linus,
Thank you for looking at the syzbot's email!
The bisection info was indeed included in this case by mistake. We have fixed this, now the bot should not mention bisections that point to release commits and thefefore won't be pinging you as the commit author.
Best Regards,
Aleksandr
On Sun, May 22, 2022 at 08:56PM -0700, Linus Torvalds wrote:
> On Sun, May 22, 2022 at 4:01 PM syzbot
> <syzbot+48135e34de22e3a82c99@syzkaller.appspotmail.com> wrote:
> >
> > The issue was bisected to:
> >
> > commit c470abd4fde40ea6a0846a2beab642a578c0b8cd
> > Author: Linus Torvalds <torvalds@linux-foundation.org>
> > Date: Sun Feb 19 22:34:00 2017 +0000
> >
> > Linux 4.10
>
> Heh. That looks very unlikely, so the bisection seems to sadly have
> failed at some point.
>
> At least one of the KASAN reports (that "final oops") does look very
> much like the bug fixed by commit 1bff51ea59a9 ("Bluetooth: fix
> use-after-free error in lock_sock_nested()"), so this may already be
> fixed, but who knows...
>
> But that "update Makefile to 4.10" is not the cause...
>
> Linus
prev parent reply other threads:[~2022-06-01 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000c1925305ac997812@google.com>
2022-05-22 23:01 ` [syzbot] KASAN: use-after-free Read in corrupted (4) syzbot
2022-05-23 3:56 ` Linus Torvalds
2022-06-01 13:51 ` Aleksandr Nogikh [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=Ypdu2H6fUOCZck1j@nogikh.google.com \
--to=nogikh@google.com \
--cc=applications@thinkbigglobal.in \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=syzbot+48135e34de22e3a82c99@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.org \
/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).