From: Paolo Abeni <pabeni@redhat.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
netdev@vger.kernel.org, Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>
Subject: Re: [PATCH net] net/sched: act_pedit: really ensure the skb is writable
Date: Wed, 04 May 2022 17:11:25 +0200 [thread overview]
Message-ID: <a8abc239076eb96ed88680dab1a1abe50a5dac7b.camel@redhat.com> (raw)
In-Reply-To: <20220504074718.146a5724@kernel.org>
On Wed, 2022-05-04 at 07:47 -0700, Jakub Kicinski wrote:
> On Wed, 04 May 2022 10:52:59 +0200 Paolo Abeni wrote:
> > On Tue, 2022-05-03 at 16:10 -0400, Jamal Hadi Salim wrote:
> > > What was the tc pedit command that triggered this?
> >
> > From the mptcp self-tests, mptcp_join.sh:
> >
> > tc -n $ns2 filter add dev ns2eth$i egress \
> > protocol ip prio 1000 \
> > handle 42 fw \
> > action pedit munge offset 148 u8 invert \
> > pipe csum tcp \
> > index 100 || exit 1
> >
> > It's used to corrupt a packet so that TCP csum is still correct while
> > the MPTCP one is not.
> >
> > The relevant part is that the touched offset is outside the skb head.
> >
> > > Can we add it to tdc tests?
> >
> > What happens in the mptcp self-tests it that an almost simultaneous
> > mptcp-level reinjection on another device using the same cloned data
> > get unintentionally corrupted and we catch it - when it sporadically
> > happens - via the MPTCP mibs.
> >
> > While we could add the above pedit command, but I fear that a
> > meaningful test for the issue addressed here not fit the tdc
> > infrastructure easily.
>
> For testing stuff like this would it be possible to inject packets
> with no headers pulled and frags in pages we marked read-only?
> We can teach netdevsim to do it.
We additionally need to ensure that the crafted packets are cloned,
otherwise the current code is AFAICS fine. And at the point we likely
want to configure the packet layout (hdrs/address) created by
netdevsim.
> Obviously not as a pre-requisite for this patch.
I agree it looks a bit out-of-scope here ;)
Paolo
next prev parent reply other threads:[~2022-05-04 15:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 14:05 [PATCH net] net/sched: act_pedit: really ensure the skb is writable Paolo Abeni
2022-05-03 20:10 ` Jamal Hadi Salim
2022-05-04 8:52 ` Paolo Abeni
2022-05-04 14:47 ` Jakub Kicinski
2022-05-04 15:11 ` Paolo Abeni [this message]
2022-05-04 15:33 ` Jakub Kicinski
2022-05-05 3:04 ` Jakub Kicinski
2022-05-05 14:13 ` Paolo Abeni
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=a8abc239076eb96ed88680dab1a1abe50a5dac7b.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).