netdev - Re: Allocation failure with subsequent kernel crash

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAP8WD_ba1k6uxSFQ00QtW0L23jzjSFw93YpEq+010zKE5sT27g@mail.gmail.com>
Date:   Mon, 20 Aug 2018 02:03:59 -0400
From:   tedheadster <tedheadster@...il.com>
To:     Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Network Development <netdev@...r.kernel.org>,
        Ingo Molnar <mingo@...hat.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>
Subject: Re: Allocation failure with subsequent kernel crash

On Mon, Aug 20, 2018 at 1:22 AM, Alexei Starovoitov
<alexei.starovoitov@...il.com> wrote:
> 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.

Alexei,
  I get this panic with two very recent kernels: 4.18.0 and 4.17.14. I
do not think this has been fixed. I am still trying to bisect it, but
sometimes it takes 5 hours for the panic to occur.

- Matthew Whitehead