From: Thomas Gleixner <tglx@linutronix.de>
To: syzbot <syzbot+c4521ac872a4ccc3afec@syzkaller.appspotmail.com>
Cc: alexander.h.duyck@intel.com, amritha.nambiar@intel.com,
andriy.shevchenko@linux.intel.com, avagin@gmail.com,
davem@davemloft.net, dmitry.torokhov@gmail.com,
dvyukov@google.com, eric.dumazet@gmail.com, f.fainelli@gmail.com,
gregkh@linuxfoundation.org, idosch@mellanox.com,
jiri@mellanox.com, kimbrownkd@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tyhicks@canonical.com,
wanghai26@huawei.com, yuehaibing@huawei.com
Subject: Re: WARNING: ODEBUG bug in netdev_freemem (2)
Date: Mon, 12 Aug 2019 21:45:39 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908122143290.7324@nanos.tec.linutronix.de> (raw)
In-Reply-To: <000000000000ea2c30058f901624@google.com>
On Wed, 7 Aug 2019, syzbot wrote:
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit: 13dfb3fa Merge git://git.kernel.org/pub/scm/linux/kernel/g..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1671e69a600000
> kernel config: https://syzkaller.appspot.com/x/.config?x=d4cf1ffb87d590d7
> dashboard link: https://syzkaller.appspot.com/bug?extid=c4521ac872a4ccc3afec
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=170542c2600000
I can't reproduce that here. Can you please apply the patch from:
https://lore.kernel.org/lkml/alpine.DEB.2.21.1906241920540.32342@nanos.tec.linutronix.de
and try to reproduce with that applied? That should give us more
information about the actual delayed work.
Thanks,
tglx
prev parent reply other threads:[~2019-08-12 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 8:53 syzbot
2019-06-24 9:33 ` Thomas Gleixner
2019-06-24 10:54 ` Dmitry Vyukov
2019-06-24 12:08 ` Eric Dumazet
2019-06-24 12:22 ` Dmitry Vyukov
2019-06-24 13:18 ` Thomas Gleixner
2019-06-24 17:27 ` Thomas Gleixner
2019-08-08 0:25 ` syzbot
2019-08-12 19:45 ` Thomas Gleixner [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=alpine.DEB.2.21.1908122143290.7324@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=alexander.h.duyck@intel.com \
--cc=amritha.nambiar@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=avagin@gmail.com \
--cc=davem@davemloft.net \
--cc=dmitry.torokhov@gmail.com \
--cc=dvyukov@google.com \
--cc=eric.dumazet@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=kimbrownkd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+c4521ac872a4ccc3afec@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tyhicks@canonical.com \
--cc=wanghai26@huawei.com \
--cc=yuehaibing@huawei.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
all inboxes | Powered by JetHome®