[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221010084946.5d32cd60@kernel.org>
Date: Mon, 10 Oct 2022 08:49:46 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Jiri Pirko <jiri@...dia.com>,
Vikas Gupta <vikas.gupta@...adcom.com>, davem@...emloft.net,
edumazet@...gle.com, pabeni@...hat.com, nicolas.dichtel@...nd.com,
gnault@...hat.com, johannes@...solutions.net,
netdev@...r.kernel.org
Subject: Re: [PATCH AUTOSEL 6.0 17/77] genetlink: hold read cb_lock during
iteration of genl_fam_idr in genl_bind()
On Sun, 9 Oct 2022 18:06:54 -0400 Sasha Levin wrote:
> In genl_bind(), currently genl_lock and write cb_lock are taken
> for iteration of genl_fam_idr and processing of static values
> stored in struct genl_family. Take just read cb_lock for this task
> as it is sufficient to guard the idr and the struct against
> concurrent genl_register/unregister_family() calls.
>
> This will allow to run genl command processing in genl_rcv() and
> mnl_socket_setsockopt(.., NETLINK_ADD_MEMBERSHIP, ..) in parallel.
Not stable material, please drop.
Powered by blists - more mailing lists