From: Weiming Shi <bestswngs@gmail.com>
To: Jon Maloy <jmaloy@redhat.com>,
Tung Nguyen <tung.quang.nguyen@est.tech>,
netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net
Cc: Xiang Mei <xmei5@asu.edu>, Weiming Shi <bestswngs@gmail.com>
Subject: [PATCH net v7 0/3] tipc: fix NULL deref in tipc_named_node_up() on empty publication list
Date: Sat, 18 Jul 2026 17:09:27 +0800 [thread overview]
Message-ID: <20260718090931.724303-1-bestswngs@gmail.com> (raw)
This series continues the fix for the NULL dereference in
tipc_named_node_up() on an empty publication list.
Patch 1/3 carries Tung Nguyen's defer-to-workqueue approach, suggested
by Jon Maloy on the thread as the replacement for the item-less bulk
from v2. Tung's RFC only exists as an inline diff in the thread, so I
folded it into this series, keeping his Signed-off-by. I tested it in
our two-node QEMU setup (veth pair, UDP bearers, node-id addressing),
both with an unprivileged user namespace and as root: the unpatched
kernel panics on the first run of the same reproducer, the patched one
distributes normally with a non-empty list.
While testing we found two residual issues in the approach, fixed by
patches 2/3 and 3/3.
Patch 2/3: tipc_net_finalize() does not check the return value of
tipc_nametbl_publish(). If the publish fails, for example on a
GFP_ATOMIC allocation failure, the node is finalized but cluster_scope
stays empty. The deferred worker then calls named_distribute() with
an empty list and hits the same NULL dereference, this time on the
workqueue. With this patch the worker re-checks the list and skips
cleanly, no crash and no link flap. The tail stamp in
named_distribute() also gets an empty-queue guard.
Patch 3/3: a repeated NODE_UP while the bulk work is pending takes a
node reference that is never dropped, because schedule_work() returns
false when the work is already queued. Found by flapping the bearer
during the defer window. One reference is leaked per repeated
NODE_UP.
Changes in v7:
- Patch 1/3: add the missing kernel-doc description for the new work
member of struct tipc_node, fixing the W=1 build warning reported
by the kernel test robot. No code change.
Changes in v6:
- Make the series self-contained: fold Tung Nguyen's base patch into
the series (1/3), keeping his Signed-off-by. The version sent as
v5 only carried the two follow-ups and depended on his patch from
the thread; the code changes in 2/3 and 3/3 are unchanged from
that version.
Changes in v5:
- Replace the item-less bulk approach with Tung Nguyen's
defer-to-workqueue RFC, which fixes the reported bug in our
testing.
- Fix two residual issues found during testing (patches 2/3, 3/3).
Weiming Shi (3):
tipc: fix NULL deref in tipc_named_node_up() on empty publication list
tipc: fix NULL deref in deferred bulk distribution on publish failure
tipc: fix node reference leak when defer work is already pending
net/tipc/core.c | 1 +
net/tipc/core.h | 2 ++
net/tipc/name_distr.c | 59 +++++++++++++++++++++++++++++++++++++++++++++++----
net/tipc/name_distr.h | 3 ++-
net/tipc/net.c | 5 ++++-
net/tipc/node.c | 35 ++++++++++++++++++++++++++++++--
6 files changed, 97 insertions(+), 8 deletions(-)
--
2.43.0
next reply other threads:[~2026-07-18 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 9:09 Weiming Shi [this message]
2026-07-18 9:09 ` [PATCH net v7 1/3] tipc: fix NULL deref in tipc_named_node_up() on empty publication list Weiming Shi
2026-07-18 9:09 ` [PATCH net v7 2/3] tipc: fix NULL deref in deferred bulk distribution on publish failure Weiming Shi
2026-07-18 9:09 ` [PATCH net v7 3/3] tipc: fix node reference leak when defer work is already pending Weiming Shi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260718090931.724303-1-bestswngs@gmail.com \
--to=bestswngs@gmail.com \
--cc=jmaloy@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=tung.quang.nguyen@est.tech \
--cc=xmei5@asu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox