From: Jakub Kicinski <kuba@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: William Liu <will@willsroot.io>,
Cong Wang <xiyou.wangcong@gmail.com>,
netdev@vger.kernel.org, stephen@networkplumber.org,
Savino Dicanosa <savy@syst3mfailure.io>
Subject: Re: [Patch net 1/2] netem: Fix skb duplication logic to prevent infinite loops
Date: Mon, 7 Jul 2025 14:26:17 -0700 [thread overview]
Message-ID: <20250707142617.10849b9e@kernel.org> (raw)
In-Reply-To: <CAM0EoM=SPbm6VdjPTTPRjtm7-gXzTvShrG=EdBiO7nCz=uJw0w@mail.gmail.com>
On Mon, 7 Jul 2025 16:49:46 -0400 Jamal Hadi Salim wrote:
> > The tc_skb_ext approach has a problem... the config option that
> > enables it is NET_TC_SKB_EXT. I assumed this is a generic name for
> > skb extensions in the tc subsystem, but unfortunately this is
> > hardcoded for NET_CLS_ACT recirculation support.
> >
> > So what this means is we have the following choices:
> > 1. Make SCH_NETEM depend on NET_CLS_ACT and NET_TC_SKB_EXT
> > 2. Add "|| IS_ENABLED(CONFIG_SCH_NETEM)" next to
> > "IS_ENABLED(CONFIG_NET_TC_SKB_EXT)" 3. Separate NET_TC_SKB_EXT and
> > the idea of recirculation support. But I'm not sure how people feel
> > about renaming config options. And this would require a small
> > change to the Mellanox driver subsystem.
> >
> > None of these sound too nice to do, and I'm not sure which approach
> > to take. In an ideal world, 3 would be best, but I'm not sure how
> > others would feel about all that just to account for a netem edge
> > case.
>
> I think you should just create a new field/type, add it here:
> include/linux/skbuff.h around line 4814 and make netem just select
> CONFIG_SKB_EXTENSIONS kconfig
> It's not the best solution but we are grasping for straws at this
> point.
Did someone report a real user of nested duplication?
Let's go ahead with the patch preventing such configurations and worry
about supporting them IIF someone actually asks.
next prev parent reply other threads:[~2025-07-07 21:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 23:13 [Patch net 0/2] netem: Fix skb duplication logic to prevent infinite loops Cong Wang
2025-07-01 23:13 ` [Patch net 1/2] " Cong Wang
2025-07-02 1:57 ` Cong Wang
2025-07-02 14:12 ` Jamal Hadi Salim
2025-07-02 15:04 ` Jamal Hadi Salim
2025-07-02 15:06 ` Jamal Hadi Salim
2025-07-02 15:20 ` William Liu
2025-07-05 0:48 ` Cong Wang
2025-07-05 13:52 ` Jamal Hadi Salim
2025-07-06 14:59 ` William Liu
2025-07-07 20:49 ` Jamal Hadi Salim
2025-07-07 21:26 ` Jakub Kicinski [this message]
2025-07-08 13:18 ` Jamal Hadi Salim
2025-07-07 19:40 ` Cong Wang
2025-07-07 20:24 ` Jamal Hadi Salim
2025-07-01 23:13 ` [Patch net 2/2] selftests/tc-testing: Add a nested netem duplicate test Cong Wang
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=20250707142617.10849b9e@kernel.org \
--to=kuba@kernel.org \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=savy@syst3mfailure.io \
--cc=stephen@networkplumber.org \
--cc=will@willsroot.io \
--cc=xiyou.wangcong@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.