From: Steffen Klassert <steffen.klassert@secunet.com>
To: Hex Rabbit <h3xrabbit@gmail.com>
Cc: Hyunwoo Kim <imv4bel@gmail.com>, <netdev@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Simon Horman <horms@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Ido Schimmel <idosch@nvidia.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v2] xfrm: esp: avoid in-place decrypt on shared skb frags
Date: Tue, 5 May 2026 07:42:18 +0200 [thread overview]
Message-ID: <afmDOrObXxUC7eDt@secunet.com> (raw)
In-Reply-To: <CAF3ZFefQM5Ud8iWDoKV9FPdZ=8V0KD56Bvkdcku1fmm6aaD_Cg@mail.gmail.com>
On Tue, May 05, 2026 at 10:49:42AM +0800, Hex Rabbit wrote:
> Hi Hyunwoo, Steffen,
>
> > The report and patch for this issue were already posted on
> > the public netdev ML 6 days ago, i.e., the bug was already
> > publicly reported:
> >
> > https://lore.kernel.org/all/afLDKSvAvMwGh7Fy@v4bel/
> >
> > Credit for patch authorship is adequately covered by
> > Signed-off-by alone. Setting aside that your work proceeded
> > independently rather than as a review of my earlier
> > submission, the trailer should conform to convention to
> > avoid future misunderstanding.
>
> For clarity, I also found and reported the issue independently to
> security@kernel.org on the same day, with my own reproducer and
> root-cause analysis. At that time I was not aware of your report or
> patch; otherwise I would have referenced it earlier.
>
> I am still not fully familiar with the exact kernel trailer convention
> here, so I added both Reported-by tags because the reports were
> independent.
>
> Steffen, either trailer form is fine with me. If you decide to drop my
> Reported-by because the patch already has my Signed-off-by, I have no
> objection.
You reported it, so you can have the tag.
This is now applied to the ipsec tree, thanks a lot everybody!
next prev parent reply other threads:[~2026-05-05 5:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-04 15:27 [PATCH net v2] xfrm: esp: avoid in-place decrypt on shared skb frags HexRabbit
2026-05-04 18:01 ` Hyunwoo Kim
2026-05-04 18:47 ` Steffen Klassert
2026-05-04 18:55 ` Hyunwoo Kim
2026-05-05 2:49 ` Hex Rabbit
2026-05-05 5:42 ` Steffen Klassert [this message]
2026-05-05 17:26 ` Hex Rabbit
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=afmDOrObXxUC7eDt@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=h3xrabbit@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=imv4bel@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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.