From: "Jiayuan Chen" <jiayuan.chen@linux.dev>
To: "Cong Wang" <xiyou.wangcong@gmail.com>
Cc: john.fastabend@gmail.com, jakub@cloudflare.com,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re:
Date: Thu, 24 Apr 2025 09:19:28 +0000 [thread overview]
Message-ID: <978f0f1e4ab0c8f46820af305f5efb00cf94ffd2@linux.dev> (raw)
In-Reply-To: <90f887391cff690e883e40cbb67a9614e7757295@linux.dev>
April 24, 2025 at 08:59, "Jiayuan Chen" <jiayuan.chen@linux.dev> wrote:
>
> April 24, 2025 at 08:40, "Cong Wang" <xiyou.wangcong@gmail.com> wrote:
>
> >
> > netdev@vger.kernel.org, bpf@vger.kernel.org
> >
> > Bcc:
> >
> >
> > Subject: test_sockmap failures on the latest bpf-next
> >
> > Reply-To:
> >
> >
> >
> > Hi all,
> >
> >
> >
> > The latest bpf-next failed on test_sockmap tests, I got the following
> >
> > failures (including 1 kernel warning). It is 100% reproducible here.
> >
> > I don't have time to look into them, a quick glance at the changelog
> >
> > shows quite some changes from Jiayuan. So please take a look, Jiayuan.
> >
> > Meanwhile, please let me know if you need more information from me.
> >
> > Thanks!
> >
> >
> >
> > --------------->
> >
>
> Thanks, I'm working on it.
>
After resetting my commit to 0bb2f7a1ad1f, which is before my changes, the warning still exists.
The warning originates from test_txmsg_redir_wait_sndmem(), which performs
'KTLS + sockmap with redir EGRESS and limited receive buffer'.
The memory charge/uncharge logic is problematic, I need some time to investigate and fix it.
Thanks.
next prev parent reply other threads:[~2025-04-24 9:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 0:40 Cong Wang
2025-04-24 0:59 ` Jiayuan Chen
2025-04-24 9:19 ` Jiayuan Chen [this message]
2025-05-19 0:30 ` test_sockmap failures on the latest bpf-next Cong Wang
-- strict thread matches above, loose matches on Subject: below --
2025-04-22 1:53 [PATCH bpf-next] bpf: Remove bpf_get_smp_processor_id_proto Alexei Starovoitov
2025-04-22 8:04 ` Feng Yang
2025-04-22 14:37 ` Alexei Starovoitov
2025-04-18 7:46 Shung-Hsi Yu
2025-04-18 7:49 ` Shung-Hsi Yu
2025-04-23 17:30 ` Re: patchwork-bot+netdevbpf
2024-06-26 6:11 Totoro W
2024-06-26 7:09 ` Eduard Zingerman
2022-05-15 20:36 [PATCH bpf-next 1/2] cpuidle/rcu: Making arch_cpu_idle and rcu_idle_exit noinstr Jiri Olsa
2023-05-20 9:47 ` Ze Gao
2023-05-21 3:58 ` Yonghong Song
2023-05-21 15:10 ` Re: Ze Gao
2023-05-21 20:26 ` Re: Jiri Olsa
2023-05-22 1:36 ` Re: Masami Hiramatsu
2023-05-22 2:07 ` Re: Ze Gao
2023-05-23 4:38 ` Re: Yonghong Song
2023-05-23 5:30 ` Re: Masami Hiramatsu
2023-05-23 6:59 ` Re: Paul E. McKenney
2023-05-25 0:13 ` Re: Masami Hiramatsu
2023-05-21 8:08 ` Re: Jiri Olsa
2023-05-21 10:09 ` Re: Masami Hiramatsu
2023-05-21 14:19 ` Re: Ze Gao
2022-03-04 8:47 Re: Harald Hauge
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=978f0f1e4ab0c8f46820af305f5efb00cf94ffd2@linux.dev \
--to=jiayuan.chen@linux.dev \
--cc=bpf@vger.kernel.org \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--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).