From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Leon Romanovsky <leon@kernel.org>, Zhu Yanjun <yanjun.zhu@intel.com>
Cc: haris.iqbal@ionos.com, jinpu.wang@ionos.com, jgg@ziepe.ca,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH 1/1] RDMA/rtrs: Require holding rcu_read_lock explicitly
Date: Tue, 19 Sep 2023 15:21:10 +0800 [thread overview]
Message-ID: <0fc1eca0-edc2-1b23-de4f-0f792cfa861f@linux.dev> (raw)
In-Reply-To: <20230919070941.GA4494@unreal>
在 2023/9/19 15:09, Leon Romanovsky 写道:
> On Mon, Sep 18, 2023 at 11:36:46PM +0800, Zhu Yanjun wrote:
>> From: Zhu Yanjun <yanjun.zhu@linux.dev>
>>
>> No functional change. The function get_next_path_rr needs to hold
>> rcu_read_lock. As such, if no rcu read lock, warnings will pop out.
>>
>> Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
>> ---
>> drivers/infiniband/ulp/rtrs/rtrs-clt.c | 7 ++++++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/infiniband/ulp/rtrs/rtrs-clt.c b/drivers/infiniband/ulp/rtrs/rtrs-clt.c
>> index b6ee801fd0ff..bc4b70318bf4 100644
>> --- a/drivers/infiniband/ulp/rtrs/rtrs-clt.c
>> +++ b/drivers/infiniband/ulp/rtrs/rtrs-clt.c
>> @@ -775,7 +775,7 @@ rtrs_clt_get_next_path_or_null(struct list_head *head, struct rtrs_clt_path *clt
>> * Related to @MP_POLICY_RR
>> *
>> * Locks:
>> - * rcu_read_lock() must be hold.
>> + * rcu_read_lock() must be held.
>> */
>> static struct rtrs_clt_path *get_next_path_rr(struct path_it *it)
>> {
>> @@ -783,6 +783,11 @@ static struct rtrs_clt_path *get_next_path_rr(struct path_it *it)
>> struct rtrs_clt_path *path;
>> struct rtrs_clt_sess *clt;
>>
>> + /*
>> + * Assert that rcu lock must be held
>> + */
>> + WARN_ON_ONCE(!rcu_read_lock_held());
> Let's use RCU_LOCKDEP_WARN(..) macro.
Got it. Will send v2 very soon.
Zhu Yanjun
>
> Thanks
>
>> +
>> clt = it->clt;
>>
>> /*
>> --
>> 2.40.1
>>
prev parent reply other threads:[~2023-09-19 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-18 15:36 [PATCH 1/1] RDMA/rtrs: Require holding rcu_read_lock explicitly Zhu Yanjun
2023-09-18 16:12 ` Jinpu Wang
2023-09-19 7:09 ` Leon Romanovsky
2023-09-19 7:21 ` Zhu Yanjun [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0fc1eca0-edc2-1b23-de4f-0f792cfa861f@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=haris.iqbal@ionos.com \
--cc=jgg@ziepe.ca \
--cc=jinpu.wang@ionos.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yanjun.zhu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox