[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201130145229.mhbkrfuvyctniaxi@linutronix.de>
Date: Mon, 30 Nov 2020 15:52:29 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Mike Galbraith <efault@....de>
Cc: Oleksandr Natalenko <oleksandr@...alenko.name>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Andrew Morton <akpm@...ux-foundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
linux-rt-users@...r.kernel.org
Subject: Re: scheduling while atomic in z3fold
On 2020-11-30 15:42:46 [+0100], Mike Galbraith wrote:
> This explodes in write_unlock() as mine did. Oleksandr's local_lock()
> variant explodes in the lock he added. (ew, corruption)
>
> I think I'll try a stable-rt tree. This master tree _should_ be fine
> given it seems to work just peachy for everything else, but my box is
> the only one making boom... and also NOT making boom with the zbud
> compressor. Hrmph.
How do you test this? I triggered a few oom-killer and I have here git
gc running for a few hours now… Everything is fine.
Sebastian
Powered by blists - more mailing lists