From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <owner-linux-mm@kvack.org>
Received: from mail-lj1-f197.google.com (mail-lj1-f197.google.com [209.85.208.197])
	by kanga.kvack.org (Postfix) with ESMTP id ADB708E0002
	for <linux-mm@kvack.org>; Mon, 14 Jan 2019 13:26:20 -0500 (EST)
Received: by mail-lj1-f197.google.com with SMTP id k16-v6so2878lji.5
        for <linux-mm@kvack.org>; Mon, 14 Jan 2019 10:26:20 -0800 (PST)
Received: from smtp.infotech.no (smtp.infotech.no. [82.134.31.41])
        by mx.google.com with ESMTP id j25-v6si982598ljc.119.2019.01.14.10.26.18
        for <linux-mm@kvack.org>;
        Mon, 14 Jan 2019 10:26:18 -0800 (PST)
Reply-To: dgilbert@interlog.com
Subject: Re: [PATCH v2] rbtree: fix the red root
References: <20190111181600.GJ6310@bombadil.infradead.org>
 <864d6b85-3336-4040-7c95-7d9615873777@lechnology.com>
 <b1033d96-ebdd-e791-650a-c6564f030ce1@lca.pw>
 <8v11ZOLyufY7NLAHDFApGwXOO_wGjVHtsbw1eiZ__YvI9EZCDe_4FNmlp0E-39lnzGQHhHAczQ6Q6lQPzVU2V6krtkblM8IFwIXPHZCuqGE=@protonmail.ch>
 <c6265fc0-4089-9d1a-ba7c-b267b847747e@interlog.com>
 <UKsodHRZU8smIdO2MHHL4Yzde_YB4iWX43TaHI1uY2tMo4nii4ucbaw4XC31XIY-Pe4oEovjF62qbkeMsIMTrvT1TdCCP4Fs_fxciAzXYVc=@protonmail.ch>
 <ad591828-76e8-324b-6ab8-dc87e4390f64@interlog.com>
 <GBn2paWQ0Uy0COgTeJsgmC18Faw0x_yNIog8gpuC5TJ4kCn_IUH1EnHJW0mQeo3Qy5MMcpMzyw9Yer3lxyWYgtk5TJx8I3sJK4oVlIJh38s=@protonmail.ch>
 <5298bfcc-0cbc-01e8-85b2-087a380fd3fe@lca.pw>
 <xeAUGwo5bQoLOJ9aXeSLY9G0hlKWJzjeZ4f4M1Hr8-1ryRwQ3Y-PgQ_eAtFAjpNZnn0zQGk6yHMkoEjjoM99vdhumv4Dey9KP5y6PvSRroo=@protonmail.ch>
 <51950f43-1daf-9192-ce9b-7a1ddae3edd2@lca.pw>
From: Douglas Gilbert <dgilbert@interlog.com>
Message-ID: <1d749c95-542f-e65d-4f1b-41d905952d77@interlog.com>
Date: Mon, 14 Jan 2019 13:26:13 -0500
MIME-Version: 1.0
In-Reply-To: <51950f43-1daf-9192-ce9b-7a1ddae3edd2@lca.pw>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-CA
Content-Transfer-Encoding: 7bit
Sender: owner-linux-mm@kvack.org
List-ID: <linux-mm.kvack.org>
To: Qian Cai <cai@lca.pw>, Esme <esploit@protonmail.ch>
Cc: David Lechner <david@lechnology.com>, Michel Lespinasse <walken@google.com>, Andrew Morton <akpm@linux-foundation.org>, "jejb@linux.ibm.com" <jejb@linux.ibm.com>, "martin.petersen@oracle.com" <martin.petersen@oracle.com>, "joeypabalinas@gmail.com" <joeypabalinas@gmail.com>, linux-mm <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>

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