[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ec93680c6a27626b23e99d552aa778be7b2ecec.camel@gmx.de>
Date: Mon, 07 Dec 2020 13:34:00 +0100
From: Mike Galbraith <efault@....de>
To: Vitaly Wool <vitaly.wool@...sulko.com>
Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Oleksandr Natalenko <oleksandr@...alenko.name>,
LKML <linux-kernel@...r.kernel.org>,
Linux-MM <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 Mon, 2020-12-07 at 12:52 +0100, Vitaly Wool wrote:
>
> Thanks. This trace beats me because I don't quite get how this could
> have happened.
I swear there's a mythical creature loose in there somewhere ;-)
Everything looks just peachy up to the instant it goes boom, then you
find in the wreckage that which was most definitely NOT there just a
few ns ago.
> Hitting write_unlock at line 341 would mean that HANDLES_ORPHANED bit
> is set but obviously it isn't.
> Could you please comment out the ".shrink = z3fold_zpool_shrink" line
> and retry?
Unfortunately, that made zero difference.
-Mike
Powered by blists - more mailing lists