From: Steffen Klassert <steffen.klassert@secunet.com>
To: Jianbo Liu <jianbol@nvidia.com>
Cc: "edumazet@google.com" <edumazet@google.com>,
Leon Romanovsky <leonro@nvidia.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"fw@strlen.de" <fw@strlen.de>
Subject: Re: [PATCH net] net: drop secpath extension before skb deferral free
Date: Tue, 21 May 2024 12:15:51 +0200 [thread overview]
Message-ID: <Zkx0V2nUonltp/pR@gauss3.secunet.de> (raw)
In-Reply-To: <14d383ebd61980ecf07430255a2de730257d3dde.camel@nvidia.com>
On Mon, May 20, 2024 at 10:06:24AM +0000, Jianbo Liu wrote:
> On Tue, 2024-05-14 at 10:51 +0200, Eric Dumazet wrote:
> >
> > I think we need a full fix, not a partial work around to an immediate
> > problem.
> >
> > Can we have some feedback from Steffen, I wonder if we missed
> > something really obvious.
> >
> > It is hard to believe this has been broken for such a long time.
>
> Could you please give me some suggestions?
Sorry for the delay, I've just returned from vacation.
I'll have a look at it.
next prev parent reply other threads:[~2024-05-21 10:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 10:02 [PATCH net] net: drop secpath extension before skb deferral free Jianbo Liu
2024-05-13 10:29 ` Eric Dumazet
2024-05-14 7:37 ` Jianbo Liu
2024-05-14 8:51 ` Eric Dumazet
2024-05-15 3:10 ` Jianbo Liu
2024-05-20 10:06 ` Jianbo Liu
2024-05-21 10:15 ` Steffen Klassert [this message]
2024-05-22 9:34 ` Steffen Klassert
2024-05-22 11:06 ` Eric Dumazet
2024-05-23 2:22 ` Jianbo Liu
2024-05-23 6:44 ` Steffen Klassert
2024-05-23 6:57 ` Jianbo Liu
2024-05-23 10:00 ` Steffen Klassert
2024-05-23 15:26 ` Jianbo Liu
2024-05-27 7:40 ` Steffen Klassert
2024-05-28 8:44 ` Steffen Klassert
2024-05-28 9:02 ` Jianbo Liu
2024-05-28 9:26 ` Steffen Klassert
2024-05-26 10:57 ` Leon Romanovsky
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=Zkx0V2nUonltp/pR@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=jianbol@nvidia.com \
--cc=leonro@nvidia.com \
--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 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.