BPF List
 help / color / mirror / Atom feed
From: "Tze-nan Wu (吳澤南)" <Tze-nan.Wu@mediatek.com>
To: "alexei.starovoitov@gmail.com" <alexei.starovoitov@gmail.com>,
	"sdf@fomichev.me" <sdf@fomichev.me>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kuniyu@amazon.com" <kuniyu@amazon.com>,
	"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"ast@kernel.org" <ast@kernel.org>,
	"Cheng-Jui Wang (王正睿)" <Cheng-Jui.Wang@mediatek.com>,
	"Chen-Yao Chang (張禎耀)" <Chen-Yao.Chang@mediatek.com>,
	wsd_upstream <wsd_upstream@mediatek.com>,
	"andrii@kernel.org" <andrii@kernel.org>,
	"Bobule Chang (張弘義)" <bobule.chang@mediatek.com>,
	"jolsa@kernel.org" <jolsa@kernel.org>,
	"daniel@iogearbox.net" <daniel@iogearbox.net>,
	"john.fastabend@gmail.com" <john.fastabend@gmail.com>,
	"Tze-nan Wu (吳澤南)" <Tze-nan.Wu@mediatek.com>,
	"song@kernel.org" <song@kernel.org>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"edumazet@google.com" <edumazet@google.com>,
	"Yanghui Li (李阳辉)" <Yanghui.Li@mediatek.com>,
	"martin.lau@linux.dev" <martin.lau@linux.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"eddyz87@gmail.com" <eddyz87@gmail.com>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"kpsingh@kernel.org" <kpsingh@kernel.org>,
	"angelogioacchino.delregno@collabora.com"
	<angelogioacchino.delregno@collabora.com>,
	"yonghong.song@linux.dev" <yonghong.song@linux.dev>,
	"haoluo@google.com" <haoluo@google.com>
Subject: Re: [PATCH net v4] bpf, net: Check cgroup_bpf_enabled() only once in do_sock_getsockopt()
Date: Thu, 29 Aug 2024 12:44:53 +0000	[thread overview]
Message-ID: <2efb1f4751fa47380d51ce538253983974a4947c.camel@mediatek.com> (raw)
In-Reply-To: <Zsk_lGsZBBqbesqS@mini-arch>

On Fri, 2024-08-23 at 19:04 -0700, Stanislav Fomichev wrote:
>  	 
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
>  On 08/22, Alexei Starovoitov wrote:
> > On Thu, Aug 22, 2024 at 12:02 AM Tze-nan Wu (吳澤南)
> > <Tze-nan.Wu@mediatek.com> wrote:
> > >
> > >
> > > BTW, If this should be handled in kernel, modification shown
> below
> > > could fix the issue without breaking the "static_branch" usage in
> both
> > > macros:
> > >
> > >
> > > +++ /include/linux/bpf-cgroup.h:
> > >     -#define BPF_CGROUP_GETSOCKOPT_MAX_OPTLEN(optlen)
> > >     +#define BPF_CGROUP_GETSOCKOPT_MAX_OPTLEN(optlen, compat)
> > >      ({
> > >             int __ret = 0;
> > >             if (cgroup_bpf_enabled(CGROUP_GETSOCKOPT))
> > >                 copy_from_sockptr(&__ret, optlen, sizeof(int));
> > >      +      else
> > >      +          *compat = true;
> > >             __ret;
> > >      })
> > >
> > >     #define BPF_CGROUP_RUN_PROG_GETSOCKOPT(sock, level, optname,
> > > optval, optlen, max_optlen, retval)
> > >      ({
> > >          int __ret = retval;
> > >     -    if (cgroup_bpf_enabled(CGROUP_GETSOCKOPT) &&
> > >     -        cgroup_bpf_sock_enabled(sock, CGROUP_GETSOCKOPT))
> > >     +    if (cgroup_bpf_sock_enabled(sock, CGROUP_GETSOCKOPT))
> > >              if (!(sock)->sk_prot->bpf_bypass_getsockopt ||
> > >                ...
> > >
> > >   +++ /net/socket.c:
> > >     int do_sock_getsockopt(struct socket *sock, bool compat, int
> level,
> > >      {
> > >         ...
> > >         ...
> > >     +     /* The meaning of `compat` variable could be changed
> here
> > >     +      * to indicate if cgroup_bpf_enabled(CGROUP_SOCK_OPS)
> is
> > > false.
> > >     +      */
> > >         if (!compat)
> > >     -       max_optlen =
> BPF_CGROUP_GETSOCKOPT_MAX_OPTLEN(optlen);
> > >     +       max_optlen = BPF_CGROUP_GETSOCKOPT_MAX_OPTLEN(optlen,
> > > &compat);
> > 
> > This is better, but it's still quite a hack. Let's not override it.
> > We can have another bool, but the question:
> > do we really need BPF_CGROUP_GETSOCKOPT_MAX_OPTLEN  ?
> > copy_from_sockptr(&__ret, optlen, sizeof(int));
> > should be fast enough to do it unconditionally.
> > What are we saving here?
> > 
> > Stan ?
> 
> Agreed, most likely nobody would notice :-)

Sorry for my late reply, just have the mailer fixed.

If it is feasible to make the `copy_from_sockptr` unconditionally,
should I submit a new patch that resolve the issue by removing
`BPF_CGROUP_GETSOCKOPT_MAX_OPTLEN`? Patch A shown as below.

  +++ /net/socket.c:
   int do_sock_getsockopt(...)
   {
  -     int max_optlen __maybe_unused;
  +     int max_optlen __maybe_unused = 0;
        const struct proto_ops *ops;
        int err;
  ...
  ...
        if (!compat) <== wonder if we should keep the condition here?
  -         max_optlen = BPF_CGROUP_GETSOCKOPT_MAX_OPTLEN(optlen);
  +         copy_from_sockptr(&max_optlen, optlen, sizeof(int));

        ops = READ_ONCE(sock->ops);
        if (level == SOL_SOCKET) {
-----------------------------------------

Or perhaps adding another variable "enabled" is the preferable way?
As it keeps the static_branch behavior.
Patch B shown as below:

  +++ /include/linux/bpf-cgroup.h:
  -#define BPF_CGROUP_GETSOCKOPT_MAX_OPTLEN(optlen)
  +#define BPF_CGROUP_GETSOCKOPT_MAX_OPTLEN(optlen, enabled)
   ({
        int __ret = 0;
        if (cgroup_bpf_enabled(CGROUP_GETSOCKOPT))
            copy_from_sockptr(&__ret, optlen, sizeof(int));
  +     else
  +         *enabled = false;
        __ret;
   })

  +++ /net/socket.c:
   int do_sock_getsockopt(...)
   {
  +   bool enabled __maybe_unused = !compat;
      int max_optlen __maybe_unused;
      const struct proto_ops *ops;
      int err;
      if (!compat)
  -       max_optlen = BPF_CGROUP_GETSOCKOPT_MAX_OPTLEN(optlen);
  +       max_optlen = BPF_CGROUP_GETSOCKOPT_MAX_OPTLEN(optlen,
&enabled);

      ops = READ_ONCE(sock->ops);
      ...
      ...
  -   if (!compat)
  +   if (enabled)
          err = BPF_CGROUP_RUN_PROG_GETSOCKOPT(...);
-----------------------------------------

Any comments would be appreciated.
--Tze-nan


  reply	other threads:[~2024-08-29 12:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21  9:30 [PATCH net v4] bpf, net: Check cgroup_bpf_enabled() only once in do_sock_getsockopt() Tze-nan Wu
2024-08-21 18:44 ` Yonghong Song
2024-08-22  3:28   ` Tze-nan Wu (吳澤南)
2024-08-21 21:01 ` Alexei Starovoitov
2024-08-22  3:16   ` Tze-nan Wu (吳澤南)
2024-08-22  7:01     ` Tze-nan Wu (吳澤南)
2024-08-22 16:00       ` Alexei Starovoitov
2024-08-24  2:04         ` Stanislav Fomichev
2024-08-29 12:44           ` Tze-nan Wu (吳澤南) [this message]
2024-08-29 16:27             ` Alexei Starovoitov

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=2efb1f4751fa47380d51ce538253983974a4947c.camel@mediatek.com \
    --to=tze-nan.wu@mediatek.com \
    --cc=Chen-Yao.Chang@mediatek.com \
    --cc=Cheng-Jui.Wang@mediatek.com \
    --cc=Yanghui.Li@mediatek.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=ast@kernel.org \
    --cc=bobule.chang@mediatek.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=eddyz87@gmail.com \
    --cc=edumazet@google.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=martin.lau@linux.dev \
    --cc=matthias.bgg@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=wsd_upstream@mediatek.com \
    --cc=yonghong.song@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