linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: whiteheadm@acm.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: Allocation failure with subsequent kernel crash
Date: Sun, 19 Aug 2018 22:22:18 -0700	[thread overview]
Message-ID: <CAADnVQJjqLY3iFy2y5mb+oMR=VHS8HS_KXa0wm1HO3v0ayvrkw@mail.gmail.com> (raw)
In-Reply-To: <CAP8WD_YEyxKOimMrGk+5Db8DpNfqQL84-2xLXbe53jiY_FoPrQ@mail.gmail.com>

On Fri, Aug 17, 2018 at 10:17 AM tedheadster <tedheadster@gmail.com> wrote:
>
> I have been trying to bisect this crash but I have not found a
> reliable reproducer. My best guess is that it was introduced after the
> 4.14 release.
>
> This is a 32 bit kernel. It is odd in that it first generates a memory
> allocation failure, and then quickly crashes with a succeeding bug.
>
> I'm including the netdev group since there is a lot of BPF stacktrace.

I don't remember vzalloc issues that was fixed in this area.
4.14 kernel is quite old. Since then syzbot found few mem
related bugs that were fixed.
please try to reproduce on the latest tree.

  reply	other threads:[~2018-08-20  5:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 17:17 Allocation failure with subsequent kernel crash tedheadster
2018-08-20  5:22 ` Alexei Starovoitov [this message]
2018-08-20  6:03   ` tedheadster
2018-08-20 19:29     ` Daniel Borkmann
2018-09-05 14:39       ` tedheadster

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='CAADnVQJjqLY3iFy2y5mb+oMR=VHS8HS_KXa0wm1HO3v0ayvrkw@mail.gmail.com' \
    --to=alexei.starovoitov@gmail.com \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=whiteheadm@acm.org \
    /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).