From: Qian Cai <quic_qiancai@quicinc.com>
To: Eric Dumazet <edumazet@google.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH v2 net-next] net: generalize skb freeing deferral to per-cpu lists
Date: Fri, 29 Apr 2022 16:44:13 -0400 [thread overview]
Message-ID: <20220429204413.GA438@qian> (raw)
In-Reply-To: <CANn89iLNpxXJMyDM-xLE_=N5jZ4jw6tfu+U++LSduUmnX7UE+g@mail.gmail.com>
On Fri, Apr 29, 2022 at 09:23:13AM -0700, Eric Dumazet wrote:
> Which tree are you using ?
linux-next tree, tag next-20220428
> Ido said the leak has been fixed in
> https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f3412b3879b4f7c4313b186b03940d4791345534
Cool, next-20220429 is running fine so far which included the patch.
next prev parent reply other threads:[~2022-04-29 20:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 20:12 [PATCH v2 net-next] net: generalize skb freeing deferral to per-cpu lists Eric Dumazet
2022-04-26 7:38 ` Paolo Abeni
2022-04-26 13:11 ` Eric Dumazet
2022-04-26 15:28 ` Paolo Abeni
2022-04-26 16:13 ` Eric Dumazet
2022-04-27 0:50 ` patchwork-bot+netdevbpf
2022-04-27 15:34 ` Ido Schimmel
2022-04-27 16:53 ` Eric Dumazet
2022-04-27 17:11 ` Eric Dumazet
2022-04-27 17:59 ` Eric Dumazet
2022-04-27 18:54 ` Eric Dumazet
2022-04-29 16:18 ` Qian Cai
2022-04-29 16:23 ` Eric Dumazet
2022-04-29 20:44 ` Qian Cai [this message]
2022-05-06 6:44 ` [net] 72fd55c0db: invoked_oom-killer:gfp_mask=0x kernel test robot
2022-05-06 8:15 ` Eric Dumazet
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=20220429204413.GA438@qian \
--to=quic_qiancai@quicinc.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@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 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).