[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c43d27e6-7953-478a-89d7-c08576443cac@web.de>
Date: Fri, 25 Jul 2025 08:48:08 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Naman Jain <namjain@...ux.microsoft.com>,
"K . Y . Srinivasan" <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>, Wei Liu <wei.liu@...nel.org>,
Dexuan Cui <decui@...rosoft.com>, Michael Kelley <mhklinux@...look.com>,
linux-hyperv@...r.kernel.org
Cc: Roman Kisel <romank@...ux.microsoft.com>,
Anirudh Rayabharam <anrayabh@...ux.microsoft.com>,
Saurabh Sengar <ssengar@...ux.microsoft.com>,
Stanislav Kinsburskii <skinsburskii@...ux.microsoft.com>,
Nuno Das Neves <nunodasneves@...ux.microsoft.com>,
Alok Tiwari <alok.a.tiwari@...cle.com>, "Paul E. McKenney"
<paulmck@...nel.org>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [v6 0/2] Drivers: hv: Introduce new driver - mshv_vtl
> I have one other usage of rcu_read_lock/unlock in the code, which I feel is fine in its current form.
You may use another lock guard accordingly, don't you?
https://elixir.bootlin.com/linux/v6.16-rc7/source/include/linux/rcupdate.h#L1155-L1167
Regards,
Markus
Powered by blists - more mailing lists