All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next] selftests: bpf: exercise bpf_mptcp_sock()
Date: Thu, 3 Mar 2022 15:31:59 +0800	[thread overview]
Message-ID: <20220303073159.GA17123@bogon> (raw)
In-Reply-To: <16274837-34e1-f382-91cd-6f646722c7c8@tessares.net>

Hi Matt,

On Tue, Mar 01, 2022 at 12:56:08PM +0100, Matthieu Baerts wrote:
> Hi Geliang,
> 
> On 24/02/2022 16:21, Geliang Tang wrote:
> > This patch extended the MPTCP test base, to exercise bpf_mptcp_sock() from
> > C test as Alexei suggested in [1].
> 
> Thank you for this patch!
> 
> > diff --git a/tools/testing/selftests/bpf/prog_tests/mptcp.c b/tools/testing/selftests/bpf/prog_tests/mptcp.c
> > index 04aef0f147dc..eba1b6d12a8c 100644
> > --- a/tools/testing/selftests/bpf/prog_tests/mptcp.c
> > +++ b/tools/testing/selftests/bpf/prog_tests/mptcp.c
> > @@ -6,6 +6,7 @@
> >  struct mptcp_storage {
> >  	__u32 invoked;
> >  	__u32 is_mptcp;
> > +	__u32 token;
> >  };
> >  
> >  static int verify_sk(int map_fd, int client_fd, const char *msg, __u32 is_mptcp)
> 
> Do you think we could verify that the token has been properly read and
> stored here? I know there were some limitations but probably we can work
> around them, no? We could store items on the msk and not the ssk for
> MPTCP connections, would that not help?

Yes, we should verify the token. Could you please give me more details
about how to store items on the msk? I don't know how the items are stored
on the ssk either, please show me which code is used to implement this.

Thanks,
-Geliang

> 
> Cheers,
> Matt
> -- 
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net
> 


  reply	other threads:[~2022-03-03  7:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 15:21 [PATCH mptcp-next] selftests: bpf: exercise bpf_mptcp_sock() Geliang Tang
2022-02-24 16:42 ` selftests: bpf: exercise bpf_mptcp_sock(): Tests Results MPTCP CI
2022-03-01 11:56 ` [PATCH mptcp-next] selftests: bpf: exercise bpf_mptcp_sock() Matthieu Baerts
2022-03-03  7:31   ` Geliang Tang [this message]
2022-03-03  9:55     ` Matthieu Baerts

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=20220303073159.GA17123@bogon \
    --to=geliang.tang@suse.com \
    --cc=matthieu.baerts@tessares.net \
    --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 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.