public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Moses <p@1g4.org>
To: netdev@vger.kernel.org
Cc: Paul Moses <p@1g4.org>
Subject: [PATCH net v1 0/3] act_gate fixes and gate selftest update
Date: Fri, 16 Jan 2026 11:25:50 +0000	[thread overview]
Message-ID: <20260116112522.159480-1-p@1g4.org> (raw)

This series fixes act_gate schedule update races by switching to an RCU
prepare-then-swap update pattern and ensures netlink dump structs are
zeroed to avoid leaking padding to userspace. It also updates the
tc-testing gate replace test to include the mandatory schedule entries
so the test suite reflects the action's strict semantics.

Paul Moses (3):
  selftests: tc-testing: fix gate replace schedule
  net/sched: act_gate: fix schedule updates with RCU swap
  net/sched: act_gate: zero-initialize netlink dump struct

 include/net/tc_act/tc_gate.h                  |  43 ++-
 net/sched/act_gate.c                          | 287 +++++++++++++-----
 .../tc-testing/tc-tests/actions/gate.json     |   2 +-
 3 files changed, 254 insertions(+), 78 deletions(-)

-- 
2.52.GIT


             reply	other threads:[~2026-01-16 11:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 11:25 Paul Moses [this message]
2026-01-16 11:25 ` [PATCH net v1 1/3] selftests: tc-testing: fix gate replace schedule Paul Moses
2026-01-16 11:26 ` [PATCH net v1 2/3] net/sched: act_gate: fix schedule updates with RCU swap Paul Moses
2026-01-19 19:12   ` [net,v1,2/3] " Jakub Kicinski
2026-01-16 11:26 ` [PATCH net v1 3/3] net/sched: act_gate: zero-initialize netlink dump struct Paul Moses
2026-01-19 19:14   ` Jakub Kicinski
2026-01-19 18:32 ` [PATCH net v1 0/3] act_gate fixes and gate selftest update Jakub Kicinski
2026-01-19 18:50   ` Paul Moses
2026-01-19 19:12     ` Jakub Kicinski

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=20260116112522.159480-1-p@1g4.org \
    --to=p@1g4.org \
    --cc=netdev@vger.kernel.org \
    /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