Re: [PATCH] zram: Fix __zram_bvec_{read,write}() locking order

swapon/913 is trying to acquire lock at zcomp_stream_get+0x5/0x90 [zram] but task is already holding lock at zs_map_object+0x7a/0x2e0 · Mikhail Gavrilov <hidden> · 2020-10-16
Re: swapon/913 is trying to acquire lock at zcomp_stream_get+0x5/0x90 [zram] but task is already holding lock at zs_map_object+0x7a/0x2e0 · Peter Zijlstra <peterz@infradead.org> · 2020-10-16
Re: swapon/913 is trying to acquire lock at zcomp_stream_get+0x5/0x90 [zram] but task is already holding lock at zs_map_object+0x7a/0x2e0 · Mikhail Gavrilov <hidden> · 2020-10-16
Re: swapon/913 is trying to acquire lock at zcomp_stream_get+0x5/0x90 [zram] but task is already holding lock at zs_map_object+0x7a/0x2e0 · Minchan Kim <minchan@kernel.org> · 2020-10-16
[PATCH] zram: Fix __zram_bvec_{read,write}() locking order · Peter Zijlstra <peterz@infradead.org> · 2020-10-19
Re: [PATCH] zram: Fix __zram_bvec_{read,write}() locking order · Minchan Kim <minchan@kernel.org> · 2020-10-19
Re: [PATCH] zram: Fix __zram_bvec_{read,write}() locking order · Sebastian Andrzej Siewior <bigeasy@linutronix.de> · 2020-10-19
Re: [PATCH] zram: Fix __zram_bvec_{read,write}() locking order · Jens Axboe <axboe@kernel.dk> · 2020-10-19

From: Minchan Kim <minchan@kernel.org>
Date: 2020-10-19 14:08:36
Also in: lkml

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 <redacted>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Tested-by: Mikhail Gavrilov <redacted>

Acked-by: Minchan Kim <minchan@kernel.org>

Thanks for the fix.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help