From: "Rafael J. Wysocki" <rafael@kernel.org>
To: syzbot <syzbot+240f9766d6be3d69431e@syzkaller.appspotmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
daniel@iogearbox.net, David Miller <davem@davemloft.net>,
devel@acpica.org, Herbert Xu <herbert@gondor.apana.org.au>,
kuznet@ms2.inr.ac.ru, Len Brown <lenb@kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
linux-can@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>, Lv <lv.zheng@intel.com>,
mkl@pengutronix.de, netdev <netdev@vger.kernel.org>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Robert Moore <robert.moore@intel.com>,
socketcan@hartkopp.net, steffen.klassert@secunet.com,
syzkaller-bugs@googlegroups.com, yoshfuji@linux-ipv6.org
Subject: Re: KASAN: slab-out-of-bounds Read in _decode_session6 (2)
Date: Fri, 22 Mar 2019 00:21:51 +0100 [thread overview]
Message-ID: <CAJZ5v0jVquKnFHrQ+=AyZM2rwOx3CkdGng1z2g2UX30+PJaKDQ@mail.gmail.com> (raw)
In-Reply-To: <000000000000461a4c0584a2cfd2@google.com>
On Fri, Mar 22, 2019 at 12:08 AM syzbot
<syzbot+240f9766d6be3d69431e@syzkaller.appspotmail.com> wrote:
>
> syzbot has bisected this bug to:
>
> commit 64fd1c7040880292710e6592ddc88d0d73cfb6fb
> Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Date: Mon Jun 12 20:48:41 2017 +0000
>
> ACPI / PM: Run wakeup notify handlers synchronously
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1555b12b200000
> start commit: 64fd1c70 ACPI / PM: Run wakeup notify handlers synchronously
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=1755b12b200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1355b12b200000
> kernel config: https://syzkaller.appspot.com/x/.config?x=93932074d01b4a5
> dashboard link: https://syzkaller.appspot.com/bug?extid=240f9766d6be3d69431e
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13f35e4d400000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1280edbd400000
>
> Reported-by: syzbot+240f9766d6be3d69431e@syzkaller.appspotmail.com
> Fixes: 64fd1c704088 ("ACPI / PM: Run wakeup notify handlers synchronously")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
I don't see how the commit turned up by the bisection can be related
to the reported crash.
prev parent reply other threads:[~2019-03-21 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000c4ba820579737025@google.com>
2019-03-21 23:08 ` KASAN: slab-out-of-bounds Read in _decode_session6 (2) syzbot
2019-03-21 23:21 ` Rafael J. Wysocki [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='CAJZ5v0jVquKnFHrQ+=AyZM2rwOx3CkdGng1z2g2UX30+PJaKDQ@mail.gmail.com' \
--to=rafael@kernel.org \
--cc=bhelgaas@google.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=devel@acpica.org \
--cc=herbert@gondor.apana.org.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
--cc=socketcan@hartkopp.net \
--cc=steffen.klassert@secunet.com \
--cc=syzbot+240f9766d6be3d69431e@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yoshfuji@linux-ipv6.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).