From: Thibaut Sautereau <thibaut.sautereau@clip-os•org>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: netdev@vger•kernel.org, linux-mm@kvack•org,
linux-kernel@vger•kernel.org,
"David S. Miller" <davem@davemloft•net>,
Laura Abbott <labbott@redhat•com>,
Kees Cook <keescook@chromium•org>,
Alexander Potapenko <glider@google•com>,
Andrew Morton <akpm@linux-foundation•org>,
clipos@ssi•gouv.fr
Subject: Re: Double free of struct sk_buff reported by SLAB_CONSISTENCY_CHECKS with init_on_free
Date: Tue, 5 Nov 2019 09:05:54 +0100 [thread overview]
Message-ID: <20191105080554.GA1006@gandi.net> (raw)
In-Reply-To: <719eebd3-259d-8beb-025a-f2d17c632711@gmail.com>
On Mon, Nov 04, 2019 at 09:33:18AM -0800, Eric Dumazet wrote:
>
>
> On 11/4/19 9:03 AM, Thibaut Sautereau wrote:
> >
> > We first encountered this issue under huge network traffic (system image
> > download), and I was able to reproduce by simply sending a big packet
> > with `ping -s 65507 <ip>`, which crashes the kernel every single time.
> >
>
> Since you have a repro, could you start a bisection ?
From my previous email:
"Bisection points to the following commit: 1b7e816fc80e ("mm: slub:
Fix slab walking for init_on_free"), and indeed the BUG is not
triggered when init_on_free is disabled."
Or are you meaning something else?
--
Thibaut Sautereau
CLIP OS developer
next prev parent reply other threads:[~2019-11-05 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 17:03 Double free of struct sk_buff reported by SLAB_CONSISTENCY_CHECKS with init_on_free Thibaut Sautereau
2019-11-04 17:33 ` Eric Dumazet
2019-11-05 8:05 ` Thibaut Sautereau [this message]
2019-11-05 10:19 ` Alexander Potapenko
2019-11-05 15:04 ` Thibaut Sautereau
2019-11-05 9:00 ` Vlastimil Babka
2019-11-05 14:32 ` Thibaut Sautereau
2019-11-05 15:02 ` Vlastimil Babka
2019-11-05 17:01 ` Laura Abbott
2019-11-06 9:29 ` Thibaut Sautereau
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=20191105080554.GA1006@gandi.net \
--to=thibaut.sautereau@clip-os$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=clipos@ssi$(echo .)gouv.fr \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=glider@google$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=labbott@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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