From: Geliang Tang <tanggeliang@kylinos.cn>

Get msk->snd_nxt with READ_ONCE() in get_subflow() of the burst schedulers.

Geliang Tang (3):
  mptcp: add mptcp_snd_nxt helper
  Squash to "bpf: Export more bpf_burst related functions"
  Squash to "selftests/bpf: Add bpf_burst scheduler"

 net/mptcp/bpf.c                                     | 1 +
 net/mptcp/protocol.c                                | 7 ++++++-
 net/mptcp/protocol.h                                | 1 +
 tools/testing/selftests/bpf/progs/mptcp_bpf_burst.c | 3 ++-
 4 files changed, 10 insertions(+), 2 deletions(-)

-- 
2.43.0

Hi Geliang,

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/9875728508

Initiator: Patchew Applier
Commits: https://github.com/multipath-tcp/mptcp_net-next/commits/f8f3a07b51e8
Patchwork: https://patchwork.kernel.org/project/mptcp/list/?series=870130


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)