netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Vyukov <dvyukov@google.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Jose Abreu <Jose.Abreu@synopsys.com>,
	syzbot <syzbot+d9536adc269404a984f8@syzkaller.appspotmail.com>,
	"arvid.brodin@alten.se" <arvid.brodin@alten.se>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"ilias.apalodimas@linaro.org" <ilias.apalodimas@linaro.org>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux@rempel-privat.de" <linux@rempel-privat.de>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"robin@protonic.nl" <robin@protonic.nl>,
	"socketcan@hartkopp.net" <socketcan@hartkopp.net>,
	"syzkaller-bugs@googlegroups.com"
	<syzkaller-bugs@googlegroups.com>
Subject: Re: KASAN: use-after-free Read in j1939_session_get_by_addr
Date: Tue, 5 Nov 2019 09:39:26 +0100	[thread overview]
Message-ID: <CACT4Y+Y+zudxSaNc4-b02QWu9hPXHrReCKsOLBpscMub5KN7+A@mail.gmail.com> (raw)
In-Reply-To: <969f940b-05ba-3fbf-79ba-95dc1cebc40d@pengutronix.de>

On Tue, Nov 5, 2019 at 9:35 AM Marc Kleine-Budde <mkl@pengutronix.de> wrote:
>
> On 11/5/19 9:21 AM, Jose Abreu wrote:
> > From: syzbot <syzbot+d9536adc269404a984f8@syzkaller.appspotmail.com>
> > Date: Nov/05/2019, 08:05:01 (UTC+00:00)
> >
> >> syzbot has bisected this bug to:
> >>
> >> commit 2af6106ae949651d529c8c3f0734c3a7babd0d4b
> >> Author: Jose Abreu <Jose.Abreu@synopsys.com>
> >> Date:   Tue Jul 9 08:03:00 2019 +0000
> >>
> >>      net: stmmac: Introducing support for Page Pool
> >
> > From the config provided, stmmac driver is not even enabled. Can you
> > please confirm the bisection process ?
>
> Looks like a false positive, as j1939 (net/can/j1939/) hit mainline with
> v5.4-rc1~131^2~78^2.
>
> While the bisected commit is v5.3-rc1~140^2~13^2.


Yes, the commit is most likely irrelevant. As you can see in the
bisection log the process was diverged by "WARNING: ODEBUG bug in
netdev_freemem". I think it's not the first and not the second time I
see that crash breaks bisection:
https://syzkaller.appspot.com/bug?id=96a64fde216dca408a5c25db4e57838c51e435aa

  reply	other threads:[~2019-11-05  8:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05  4:22 KASAN: use-after-free Read in j1939_session_get_by_addr syzbot
2019-11-05  8:05 ` syzbot
2019-11-05  8:21   ` Jose Abreu
2019-11-05  8:33     ` Marc Kleine-Budde
2019-11-05  8:39       ` Dmitry Vyukov [this message]
2023-07-11 13:52 ` [syzbot] " syzbot
2023-07-25 13:53 ` syzbot
2023-08-08 14:34   ` Aleksandr Nogikh
2023-08-08 13:54 ` syzbot
2023-11-06 14:35 ` syzbot
2023-11-20 14:35 ` syzbot
2023-12-04 14:35 ` syzbot
2023-12-18 14:36 ` syzbot

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+Y+zudxSaNc4-b02QWu9hPXHrReCKsOLBpscMub5KN7+A@mail.gmail.com \
    --to=dvyukov@google.com \
    --cc=Jose.Abreu@synopsys.com \
    --cc=arvid.brodin@alten.se \
    --cc=davem@davemloft.net \
    --cc=ilias.apalodimas@linaro.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=robin@protonic.nl \
    --cc=socketcan@hartkopp.net \
    --cc=syzbot+d9536adc269404a984f8@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).