[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1908072248410.24014@nanos.tec.linutronix.de>
Date: Wed, 7 Aug 2019 22:52:31 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Austin Kim <austindh.kim@...il.com>
cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Sasha Levin <sashal@...nel.org>, peterz@...radead.org,
mingo@...nel.org, tj@...nel.org, jiangshanlai@...il.com,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
#¼ÇüÁø <mike.seo@....com>
Subject: Re: NULL ptr deref in wq_worker_sleeping on 4.19
On Wed, 7 Aug 2019, Austin Kim wrote:
Again:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
> Is it possible for you to generate kernel patch only with **kernel
> log** for 'use-after-free' case?
What? I have no idea how to reproduce that issue so how should I create a
kernel patch for something which can happen at some random place in several
million lines of code?
> With kernel log, we only have limited information, so it is hard to
> debug 'use-after-free' case with this signature.
My information is even more limited...
Thanks,
tglx
Powered by blists - more mailing lists