[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201019140830.GA3118409@google.com>
Date: Mon, 19 Oct 2020 07:08:30 -0700
From: Minchan Kim <minchan@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
linux-block@...r.kernel.org,
Mike Galbraith <umgwanakikbuti@...il.com>, ngupta@...are.org,
sergey.senozhatsky.work@...il.com, bigeasy@...utronix.de,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] zram: Fix __zram_bvec_{read,write}() locking order
On Mon, Oct 19, 2020 at 12:13:53PM +0200, Peter Zijlstra wrote:
>
> Mikhail reported a lockdep spat detailing how __zram_bvec_read() and
> __zram_bvec_write() use zstrm->lock and zspage->lock in opposite order.
>
> Reported-by: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org>
> Tested-by: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
Acked-by: Minchan Kim <minchan@...nel.org>
Thanks for the fix.
Powered by blists - more mailing lists