|
On Thu, Oct 27, 2022 at 12:55 PM Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
>
> I think we need to update this code to squeeze in a del_timer_shutdown() to
> make sure that the timers are never restarted.
So the reason the networking code does this is that it can't just do
the old 'sync()' thing, the timers are deleted in contexts where that
isn't valid.
Which is also afaik why the networking code does that whole "timer
implies a refcount to the socket" and then does the
if (del_timer(timer))
sock_put()
thing (ie if the del_timer failed - possibly because it was already
running - you leave the refcount alone).
So the networking code cannot do the del_timer_shutdown() for the same
reason it cannot do the del_timer_sync(): it can't afford to wait for
the timer to stop running.
I suspect it needs something like a new "del_timer_shutdown_async()"
that isn't synchronous, but does that
- acts as del_timer in that it doesn't wait, and returns a success if
it could just remove the pending case
- does that "mark timer for shutdown" in that success case
or something similar.
But the networking people will know better.
Linus
|
