RE: [PATCH net v8 3/3] tipc: fix node reference leak when defer work is already pending

[Tung Quang Nguyen]

>Subject: [PATCH net v8 3/3] tipc: fix node reference leak when defer work is
>already pending
>
>In tipc_node_write_unlock(), TIPC_NOTIFY_NODE_UP with an empty
>cluster_scope takes a node reference and schedules n->work. If the link flaps
>down and up while that work is still pending, the next NODE_UP takes another
>reference, but schedule_work() returns false and the extra reference is never
>dropped. The tipc_node structure leaks.
>
>Verified by flapping the bearer while the work is pending: one reference is
>leaked per repeated NODE_UP, while the work is put only once when it finally
>runs.
>
>Drop the reference when the work was already queued.
>
>Reported-by: Xiang Mei <xmei5@xxxxxxx>
>Assisted-by: Claude:claude-opus-4-8
>Signed-off-by: Weiming Shi <bestswngs@xxxxxxxxx>
Please drop this patch because sashiko reports the same issue for patch 1/3: https://sashiko.dev/#/patchset/20260718092544.785289-1-bestswngs%40gmail.com