linux-kernel - Re: [PATCH v2] rbtree: fix the red root

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: <1d749c95-542f-e65d-4f1b-41d905952d77@interlog.com>
Date:   Mon, 14 Jan 2019 13:26:13 -0500
From:   Douglas Gilbert <dgilbert@...erlog.com>
To:     Qian Cai <cai@....pw>, Esme <esploit@...tonmail.ch>
Cc:     David Lechner <david@...hnology.com>,
        Michel Lespinasse <walken@...gle.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "jejb@...ux.ibm.com" <jejb@...ux.ibm.com>,
        "martin.petersen@...cle.com" <martin.petersen@...cle.com>,
        "joeypabalinas@...il.com" <joeypabalinas@...il.com>,
        linux-mm <linux-mm@...ck.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] rbtree: fix the red root

On 2019-01-14 12:58 p.m., Qian Cai wrote:
> Unfortunately, I could not trigger any of those here both in a bare-metal and
> virtual machines. All I triggered were hung tasks and soft-lockup due to fork bomb.
> 
> The only other thing I can think of is to setup kdump to capture a vmcore when
> either GPF or BUG() happens, and then share the vmcore somewhere, so I might
> pork around to see where the memory corruption looks like.

Another question that I forgot to ask, what type of device is /dev/sg0 ?
On a prior occasion (KASAN, throw spaghetti ...) it was a SATA device
and the problem was in libata.

Doug Gilbert