From: Dave Jones <davej@codemonkey.org.uk>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org
Subject: Re: kasan r8169 use-after-free trace.
Date: Thu, 12 Nov 2015 11:24:59 -0500 [thread overview]
Message-ID: <20151112162459.GA20797@codemonkey.org.uk> (raw)
In-Reply-To: <20151111091928.GA14531@electric-eye.fr.zoreil.com>
On Wed, Nov 11, 2015 at 10:19:28AM +0100, Francois Romieu wrote:
> Dave Jones <davej@codemonkey.org.uk> :
> > This happens during boot, (and then there's a flood of traces that happen so fast
> > afterwards it completely overwhelms serial console; not sure if they're the
> > same/related or not).
> >
> > ==================================================================
> > BUG: KASAN: use-after-free in rtl8169_poll+0x4b6/0xb70 at addr ffff8801d43b3288
> > Read of size 1 by task kworker/0:3/188
> > =============================================================================
> > BUG kmalloc-256 (Not tainted): kasan: bad access detected
> > -----------------------------------------------------------------------------
> >
> > Disabling lock debugging due to kernel taint
> > INFO: Slab 0xffffea000750ecc0 objects=16 used=16 fp=0x (null) flags=0x8000000000000080
> > INFO: Object 0xffff8801d43b3200 @offset=512 fp=0xffff8801d43b3800
> >
> > Bytes b4 ffff8801d43b31f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> > Object ffff8801d43b3200: 00 38 3b d4 01 88 ff ff 00 00 00 00 00 00 00 00 .8;.............
>
> Does the patch below cure it ?
It did, thanks for the quick turnaround! It also turns out this was responsible
for the flood of spew afterwards. It's completely silent when I apply your diff.
Dave
prev parent reply other threads:[~2015-11-12 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 3:30 kasan r8169 use-after-free trace Dave Jones
2015-11-11 9:19 ` Francois Romieu
2015-11-11 13:16 ` Eric Dumazet
2015-11-11 15:34 ` Corinna Vinschen
2015-11-12 16:24 ` Dave Jones [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=20151112162459.GA20797@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.