From: Matthieu Baerts <matttbe@kernel.org>
To: Geliang Tang <geliang@kernel.org>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH bpf-next] selftests/bpf: Add pid limit for mptcpify prog
Date: Thu, 4 Apr 2024 12:55:40 +0200 [thread overview]
Message-ID: <51250875-3dcd-49be-af94-b918eb6ac27c@kernel.org> (raw)
In-Reply-To: <3cb9d44995621e0cf598146875706480e620dc57.camel@kernel.org>
Hi Geliang,
On 03/04/2024 03:00, Geliang Tang wrote:
> Hi Matt,
>
> On Tue, 2024-04-02 at 17:10 +0000, patchwork-bot+netdevbpf@kernel.org
> wrote:
>> Hello:
>>
>> This patch was applied to bpf/bpf-next.git (master)
>> by Andrii Nakryiko <andrii@kernel.org>:
>>
>> On Tue, 2 Apr 2024 18:50:21 +0800 you wrote:
>>> From: Geliang Tang <tanggeliang@kylinos.cn>
>>>
>>> In order to prevent mptcpify prog from affecting the running
>>> results
>>> of other BPF tests, a pid limit was added to restrict it from only
>>> modifying its own program.
>>>
>>> Signed-off-by: Geliang Tang <tanggeliang@kylinos.cn>
>>> Suggested-by: Martin KaFai Lau <martin.lau@kernel.org>
>>>
>>> [...]
>>
>> Here is the summary with links:
>> - [bpf-next] selftests/bpf: Add pid limit for mptcpify prog
>> https://git.kernel.org/bpf/bpf-next/c/c07b4bcd5163
>>
>> You are awesome, thank you!
>
> Please also merge this patch into our MPTCP export branch, since some
> patches in our patchwork depond on it.
>
> These two patches need to be merged too:
>
> selftests/bpf: Use connect_fd_to_fd in bpf_tcp_ca
> selftests/bpf: Drop settimeo in do_test
>
> I changed the states of them all as "Queued" and delegated them to you
> in our patchwork.
I thought the bpf-next tree was synced with net-next every week, but no.
So I just added them in our tree ('fixes for net-next', but that's
temporally).
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
prev parent reply other threads:[~2024-04-04 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 10:50 [PATCH bpf-next] selftests/bpf: Add pid limit for mptcpify prog Geliang Tang
2024-04-02 11:43 ` MPTCP CI
2024-04-02 17:10 ` patchwork-bot+netdevbpf
2024-04-03 1:00 ` Geliang Tang
2024-04-04 10:55 ` Matthieu Baerts [this message]
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=51250875-3dcd-49be-af94-b918eb6ac27c@kernel.org \
--to=matttbe@kernel.org \
--cc=geliang@kernel.org \
--cc=mptcp@lists.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).