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 1/3] Squash to "bpf: Add bpf_mptcp_sched_ops"
Date: Thu, 3 Aug 2023 15:36:24 +0800	[thread overview]
Message-ID: <20230803073624.GA6125@bogon> (raw)
In-Reply-To: <1bf9dba1-095a-41ae-ac25-6dc05918806f@tessares.net>

On Thu, Aug 03, 2023 at 09:25:42AM +0200, Matthieu Baerts wrote:
> Hi Geliang,
> 
> On 02/08/2023 07:10, Geliang Tang wrote:
> > No need to change subflow->stale bit-filed now, so drop the writing
> > access of it.
> 
> Just to be sure, do I still need to apply this patch that is no longer
> part of the v2 series?

Yes, this patch is still needed. Please apply it to the export branch.

Thanks,
-Geliang
> 
> Cheers,
> Matt
> 
> > Signed-off-by: Geliang Tang <geliang.tang@suse.com>
> > ---
> >  net/mptcp/bpf.c | 3 ---
> >  1 file changed, 3 deletions(-)
> > 
> > diff --git a/net/mptcp/bpf.c b/net/mptcp/bpf.c
> > index 51634efe4741..5c82cc35bfe0 100644
> > --- a/net/mptcp/bpf.c
> > +++ b/net/mptcp/bpf.c
> > @@ -52,9 +52,6 @@ static int bpf_mptcp_sched_btf_struct_access(struct bpf_verifier_log *log,
> >  	case offsetof(struct mptcp_subflow_context, scheduled):
> >  		end = offsetofend(struct mptcp_subflow_context, scheduled);
> >  		break;
> > -	case offsetofend(struct mptcp_subflow_context, map_csum_len):
> > -		end = offsetof(struct mptcp_subflow_context, data_avail);
> > -		break;
> >  	case offsetof(struct mptcp_subflow_context, avg_pacing_rate):
> >  		end = offsetofend(struct mptcp_subflow_context, avg_pacing_rate);
> >  		break;
> 
> -- 
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net

  reply	other threads:[~2023-08-03  7:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02  5:10 [PATCH mptcp-next 0/3] add bpf_stale scheduler Geliang Tang
2023-08-02  5:10 ` [PATCH mptcp-next 1/3] Squash to "bpf: Add bpf_mptcp_sched_ops" Geliang Tang
2023-08-02 16:52   ` Mat Martineau
2023-08-03  7:25   ` Matthieu Baerts
2023-08-03  7:36     ` Geliang Tang [this message]
2023-08-04 12:27       ` Matthieu Baerts
2023-08-02  5:10 ` [PATCH mptcp-next 2/3] selftests/bpf: Add bpf_stale scheduler Geliang Tang
2023-08-02 17:08   ` Mat Martineau
2023-08-02  5:10 ` [PATCH mptcp-next 3/3] selftests/bpf: Add bpf_stale test Geliang Tang
2023-08-02  6:19   ` selftests/bpf: Add bpf_stale test: Tests Results 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=20230803073624.GA6125@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.