From: MPTCP CI <wpasupplicant.patchew@gmail.com>
To: Edward Adam Davis <eadavis@qq.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH V4] mptcp: pm: Fix uaf in __timer_delete_sync
Date: Tue, 10 Sep 2024 10:54:39 +0000 [thread overview]
Message-ID: <ea2d4e0b-efe9-f7fa-08a3-4951aa698dcc@gmail.com> (raw)
In-Reply-To: <tencent_24C00657C9AC2EC62EF90C8E27F446C69206@qq.com>
Hi Edward,
Thank you for your modifications, that's great!
Our CI did some validations and here is its report:
- KVM Validation: normal: Success! ✅
- KVM Validation: debug: Success! ✅
- KVM Validation: btf (only bpftest_all): Success! ✅
- Task: https://github.com/multipath-tcp/mptcp_net-next/actions/runs/10790389747
Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/e58211a3272b
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=888810
If there are some issues, you can reproduce them using the same environment as
the one used by the CI thanks to a docker image, e.g.:
$ cd [kernel source code]
$ docker run -v "${PWD}:${PWD}:rw" -w "${PWD}" --privileged --rm -it \
--pull always mptcp/mptcp-upstream-virtme-docker:latest \
auto-normal
For more details:
https://github.com/multipath-tcp/mptcp-upstream-virtme-docker
Please note that despite all the efforts that have been already done to have a
stable tests suite when executed on a public CI like here, it is possible some
reported issues are not due to your modifications. Still, do not hesitate to
help us improve that ;-)
Cheers,
MPTCP GH Action bot
Bot operated by Matthieu Baerts (NGI0 Core)
next prev parent reply other threads:[~2024-09-10 10:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 13:13 [syzbot] [mptcp?] KASAN: slab-use-after-free Read in __timer_delete_sync syzbot
2024-09-03 15:09 ` [PATCH] mptcp: pm: Fix uaf " Edward Adam Davis
2024-09-03 15:18 ` Eric Dumazet
2024-09-04 0:52 ` Edward Adam Davis
2024-09-04 1:01 ` [PATCH V2] " Edward Adam Davis
2024-09-04 1:52 ` MPTCP CI
2024-09-04 20:39 ` Matthieu Baerts
2024-09-05 12:27 ` [PATCH net v3] " Edward Adam Davis
2024-09-05 13:20 ` MPTCP CI
2024-09-05 14:52 ` MPTCP CI
2024-09-06 18:55 ` Matthieu Baerts
2024-09-06 22:02 ` Jakub Kicinski
2024-09-09 7:01 ` Matthieu Baerts
2024-09-09 13:07 ` Paolo Abeni
2024-09-10 3:59 ` Edward Adam Davis
2024-09-10 9:58 ` [PATCH V4] " Edward Adam Davis
2024-09-10 10:54 ` MPTCP CI [this message]
2024-09-10 9:58 ` [PATCH net " Edward Adam Davis
2024-09-10 10:51 ` MPTCP CI
2024-09-10 11:27 ` Paolo Abeni
2024-09-10 14:29 ` Matthieu Baerts
2024-09-11 23:20 ` patchwork-bot+netdevbpf
2024-09-05 12:35 ` [PATCH V2] " Edward Adam Davis
2024-09-03 16:03 ` [PATCH] " MPTCP CI
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=ea2d4e0b-efe9-f7fa-08a3-4951aa698dcc@gmail.com \
--to=wpasupplicant.patchew@gmail.com \
--cc=eadavis@qq.com \
--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