From: Dmitry Vyukov <dvyukov@google.com>
To: Jon Maloy <jon.maloy@ericsson.com>
Cc: syzbot <syzbot+9d4c12bfd45a58738d0a@syzkaller.appspotmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"dsahern@gmail.com" <dsahern@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"pablo@netfilter.org" <pablo@netfilter.org>,
"syzkaller-bugs@googlegroups.com"
<syzkaller-bugs@googlegroups.com>,
"tipc-discussion@lists.sourceforge.net"
<tipc-discussion@lists.sourceforge.net>,
"ying.xue@windriver.com" <ying.xue@windriver.com>
Subject: Re: general protection fault in dst_dev_put (2)
Date: Wed, 20 Mar 2019 17:36:11 +0100 [thread overview]
Message-ID: <CACT4Y+Zrr6AHWh6+ULMoY_Vrpkb0yAjO0nBd-C-=iiYsSWwVEg@mail.gmail.com> (raw)
In-Reply-To: <BL0PR1501MB200344EF36F7E6EFCE435F4E9A410@BL0PR1501MB2003.namprd15.prod.outlook.com>
On Wed, Mar 20, 2019 at 4:43 PM Jon Maloy <jon.maloy@ericsson.com> wrote:
>
> This one points to a bug that was fixed in commit dc4501ff2875 ("tipc: fix a double free in tipc_enable_bearer()").
> That commit was applied to 4.20, but is not present in 4.16, which caused this dump.
> To get further with this I need a dump of the actual crash in 4.20 or 5.0.
> Maybe we are looking at two different problems here?
Hi Jon,
The latest crashes are available on the syzbot dashboard (see dashbolard link).
>
> ///jon
>
>
>
> > -----Original Message-----
> > From: netdev-owner@vger.kernel.org <netdev-owner@vger.kernel.org>
> > On Behalf Of syzbot
> > Sent: 19-Mar-19 18:24
> > To: davem@davemloft.net; dsahern@gmail.com; Jon Maloy
> > <jon.maloy@ericsson.com>; linux-kernel@vger.kernel.org;
> > netdev@vger.kernel.org; pablo@netfilter.org; syzkaller-
> > bugs@googlegroups.com; tipc-discussion@lists.sourceforge.net;
> > ying.xue@windriver.com
> > Subject: Re: general protection fault in dst_dev_put (2)
> >
> > syzbot has bisected this bug to:
> >
> > commit 52dfae5c85a4c1078e9f1d5e8947d4a25f73dd81
> > Author: Jon Maloy <jon.maloy@ericsson.com>
> > Date: Thu Mar 22 19:42:52 2018 +0000
> >
> > tipc: obtain node identity from interface by default
> >
> > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1631fc2b200000
> > start commit: 52dfae5c tipc: obtain node identity from interface by defa..
> > git tree: upstream
> > final crash: https://syzkaller.appspot.com/x/report.txt?x=1531fc2b200000
> > console output: https://syzkaller.appspot.com/x/log.txt?x=1131fc2b200000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=8f00801d7b7c4fe6
> > dashboard link:
> > https://syzkaller.appspot.com/bug?extid=9d4c12bfd45a58738d0a
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17254878c00000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=171ca5df400000
> >
> > Reported-by: syzbot+9d4c12bfd45a58738d0a@syzkaller.appspotmail.com
> > Fixes: 52dfae5c ("tipc: obtain node identity from interface by default")
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/BL0PR1501MB200344EF36F7E6EFCE435F4E9A410%40BL0PR1501MB2003.namprd15.prod.outlook.com.
> For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2019-03-20 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 15:21 general protection fault in dst_dev_put (2) syzbot
2019-03-19 17:24 ` syzbot
2019-03-20 15:43 ` Jon Maloy
2019-03-20 16:36 ` Dmitry Vyukov [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='CACT4Y+Zrr6AHWh6+ULMoY_Vrpkb0yAjO0nBd-C-=iiYsSWwVEg@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=jon.maloy@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzbot+9d4c12bfd45a58738d0a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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).