[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <168598854044.127564.8532399641861277056.b4-ty@kernel.dk>
Date: Mon, 05 Jun 2023 12:09:00 -0600
From: Jens Axboe <axboe@...nel.dk>
To: tj@...nel.org, josef@...icpanda.com, linan666@...weicloud.com
Cc: cgroups@...r.kernel.org, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, linan122@...wei.com,
yukuai3@...wei.com, yi.zhang@...wei.com, houtao1@...wei.com,
yangerkun@...wei.com
Subject: Re: [PATCH] blk-iocost: use spin_lock_irqsave in
adjust_inuse_and_calc_cost
On Sat, 27 May 2023 17:19:04 +0800, linan666@...weicloud.com wrote:
> adjust_inuse_and_calc_cost() use spin_lock_irq() and IRQ will be enabled
> when unlock. DEADLOCK might happen if we have held other locks and disabled
> IRQ before invoking it.
>
> Fix it by using spin_lock_irqsave() instead, which can keep IRQ state
> consistent with before when unlock.
>
> [...]
Applied, thanks!
[1/1] blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
commit: 8d211554679d0b23702bd32ba04aeac0c1c4f660
Best regards,
--
Jens Axboe
Powered by blists - more mailing lists