From: Douglas Gilbert <dgilbert@interlog.com>
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>
Subject: Re: [PATCH v2] rbtree: fix the red root
Date: Mon, 14 Jan 2019 13:26:13 -0500 [thread overview]
Message-ID: <1d749c95-542f-e65d-4f1b-41d905952d77@interlog.com> (raw)
In-Reply-To: <51950f43-1daf-9192-ce9b-7a1ddae3edd2@lca.pw>
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
next prev parent reply other threads:[~2019-01-14 18:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YrcPMrGmYbPe_xgNEV6Q0jqc5XuPYmL2AFSyeNmg1gW531bgZnBGfEUK5_ktqDBaNW37b-NP2VXvlliM7_PsBRhSfB649MaW1Ne7zT9lHc=@protonmail.ch>
2019-01-11 16:51 ` [PATCH] " Qian Cai
2019-01-11 17:17 ` Joey Pabalinas
2019-01-11 17:31 ` Matthew Wilcox
2019-01-11 17:53 ` Joey Pabalinas
2019-01-11 18:12 ` Qian Cai
2019-01-11 18:12 ` Qian Cai
2019-01-11 18:16 ` Matthew Wilcox
2019-01-11 18:16 ` Matthew Wilcox
2019-01-11 20:58 ` [PATCH v2] " Qian Cai
2019-01-11 23:16 ` Matthew Wilcox
2019-01-12 0:18 ` Qian Cai
2019-01-12 0:39 ` Esme
2019-01-11 23:47 ` David Lechner
2019-01-12 2:58 ` Michel Lespinasse
2019-01-12 2:58 ` Michel Lespinasse
2019-01-14 2:20 ` David Lechner
2019-01-14 2:33 ` Qian Cai
2019-01-14 3:07 ` Esme
2019-01-14 3:52 ` Douglas Gilbert
2019-01-14 3:59 ` Esme
2019-01-14 4:52 ` Douglas Gilbert
2019-01-14 6:23 ` Esme
2019-01-14 15:45 ` Qian Cai
2019-01-14 15:51 ` Esme
2019-01-14 17:58 ` Qian Cai
2019-01-14 18:26 ` Douglas Gilbert [this message]
2019-01-15 5:31 ` Qian Cai
2019-01-16 14:37 ` Esme
2019-01-18 17:10 ` Qian Cai
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=1d749c95-542f-e65d-4f1b-41d905952d77@interlog.com \
--to=dgilbert@interlog.com \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=david@lechnology.com \
--cc=esploit@protonmail.ch \
--cc=jejb@linux.ibm.com \
--cc=joeypabalinas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=martin.petersen@oracle.com \
--cc=walken@google.com \
/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