[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cc6274c3-b9ba-cd6e-5ef4-af736b1a1f13@huaweicloud.com>
Date: Mon, 30 Oct 2023 21:16:19 +0800
From: Yu Kuai <yukuai1@...weicloud.com>
To: Ming Lei <ming.lei@...hat.com>, Yu Kuai <yukuai1@...weicloud.com>
Cc: linan666@...weicloud.com, josef@...icpanda.com, axboe@...nel.dk,
linux-block@...r.kernel.org, nbd@...er.debian.org,
linux-kernel@...r.kernel.org, linan122@...wei.com,
yi.zhang@...wei.com, houtao1@...wei.com, yangerkun@...wei.com,
"yukuai (C)" <yukuai3@...wei.com>
Subject: Re: [PATCH] nbd: pass nbd_sock to nbd_read_reply() instead of index
在 2023/10/30 20:42, Ming Lei 写道:
>> After reviewing some code, I found that it's wrong to grab config_lock,
>> because other context will grab such lock and flush_workqueue(), and
>> there is no gurantee that recv_work() will grab the lock first.
>>
>> Will it be acceptable to export blk_queue_enter()? I can't think of
>> other way to retrieve the`nsock` reference at the entry of recv_work().
>
> Then I think it is easier to pass `nsock` from `recv_thread_args`, which
> can be thought as local variable too.
>
> Reviewed-by: Ming Lei <ming.lei@...hat.com>
Agreed
Reviewed-by: Yu Kuai <yukuai3@...wei.com>
Powered by blists - more mailing lists