[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y15KC8Zb3rHlfTPu@infradead.org>
Date: Sun, 30 Oct 2022 02:55:23 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Yu Kuai <yukuai1@...weicloud.com>
Cc: tj@...nel.org, josef@...icpanda.com, axboe@...nel.dk,
yukuai3@...wei.com, cgroups@...r.kernel.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
yi.zhang@...wei.com
Subject: Re: [PATCH -next 4/5] blk-iocost: fix sleeping in atomic context
warnning in ioc_qos_write()
This seems a little convoluted to me. I'd suggest to add a new
sleeping lock that protects the updates, then you just take the
spinlock after parsing without much other changes.
(The same comment also applies to patch 5).
Powered by blists - more mailing lists