From: Martin KaFai Lau <martin.lau@linux.dev>
To: Jiayuan Chen <mrpre@163.com>, Jakub Kicinski <kuba@kernel.org>
Cc: edumazet@google.com, jakub@cloudflare.com, davem@davemloft.net,
dsahern@kernel.org, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, horms@kernel.org,
daniel@iogearbox.net, mykolal@fb.com, ast@kernel.org,
kpsingh@kernel.org, jolsa@kernel.org, eddyz87@gmail.com,
shuah@kernel.org, sdf@fomichev.me,
linux-kselftest@vger.kernel.org, haoluo@google.com,
song@kernel.org, john.fastabend@gmail.com, andrii@kernel.org,
mhal@rbox.co, yonghong.song@linux.dev
Subject: Re: [PATCH bpf v4 0/2] bpf: fix recursive lock and add test
Date: Mon, 18 Nov 2024 13:39:16 -0800 [thread overview]
Message-ID: <ba7c39cb-18ab-4c51-a4cb-89769ea09e6b@linux.dev> (raw)
In-Reply-To: <20241118030910.36230-1-mrpre@163.com>
On 11/17/24 7:09 PM, Jiayuan Chen wrote:
> 1. fix recursive lock when ebpf prog return SK_PASS.
> 2. add selftest to reproduce recursive lock.
>
> Note that the test code can reproduce the 'dead-lock' and if just
> the selftest merged without first patch, the test case will
> definitely fail, because the issue of deadlock is inevitable.
Acked-by: Martin KaFai Lau <martin.lau@kernel.org>
Jakub, please help to land it to the net tree. Thanks!
next prev parent reply other threads:[~2024-11-18 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 3:09 [PATCH bpf v4 0/2] bpf: fix recursive lock and add test Jiayuan Chen
2024-11-18 3:09 ` [PATCH bpf v4 1/2] bpf: fix recursive lock when verdict program return SK_PASS Jiayuan Chen
2024-11-18 3:09 ` [PATCH bpf v4 2/2] selftests/bpf: Add some tests with sockmap SK_PASS Jiayuan Chen
2024-11-18 21:39 ` Martin KaFai Lau [this message]
2024-11-19 4:00 ` [PATCH bpf v4 0/2] bpf: fix recursive lock and add test patchwork-bot+netdevbpf
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=ba7c39cb-18ab-4c51-a4cb-89769ea09e6b@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=horms@kernel.org \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhal@rbox.co \
--cc=mrpre@163.com \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.