Thread (23 messages) flat view 23 messages, 3 authors, 2021-10-06

Re: [PATCH net-next v2 3/5] devlink: Allow set specific ops callbacks dynamically

From: Jakub Kicinski <kuba@kernel.org>
Date: 2021-10-06 13:36:03
Also in: linux-rdma, lkml

On Wed, 6 Oct 2021 06:37:44 +0300 Leon Romanovsky wrote:
Let's chose random kernel version (v5.11)
https://elixir.bootlin.com/linux/v5.11/source/net/core/devlink.c#L10245
as you can see, it doesn't hold ANY driver core locks,
Nope, that is not what I see.
so it can be called in any time during driver .probe() or .remove(). 
Having a callback invoked after registering to a subsystem (which used
to be the case for devlink before the changes) is _normal_.

You keep talking about .probe() like it's some magic period of complete
quiescence.
Drivers that have implemented ops.flash_update() have no idea about that.
I bet.

I don't think this discussion is going anywhere, count me out.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help