All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next] mptcp: support SYSCTL only if enabled
Date: Thu, 29 Apr 2021 17:07:09 -0700 (PDT)	[thread overview]
Message-ID: <9c92075-e759-baed-c1a5-7f167bfa60f9@linux.intel.com> (raw)
In-Reply-To: <20210429145912.2022531-1-matthieu.baerts@tessares.net>

On Thu, 29 Apr 2021, Matthieu Baerts wrote:

> Since the introduction of the sysctl support in MPTCP with
> commit 784325e9f037 ("mptcp: new sysctl to control the activation per NS"),
> we don't check CONFIG_SYSCTL.
>
> Until now, that was not an issue: the register and unregister functions
> were replaced by NO-OP one if SYSCTL was not enabled in the config. The
> only thing we could have avoid is not to reserve memory for the table
> but that's for the moment only a small table per net-ns.
>
> But the following commit is going to use SYSCTL_ZERO and SYSCTL_ONE
> which are not be defined if SYSCTL is not enabled in the config. This
> causes 'undefined reference' errors from the linker.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
> ---
>
> Notes:
>    The "following" commit is "mptcp: restrict values of 'enabled' sysctl".
>
>    The goal is to place this patch before this commit.
>
> net/mptcp/ctrl.c | 28 ++++++++++++++++++++++------
> 1 file changed, 22 insertions(+), 6 deletions(-)
>

Looks good to me, thanks Matthieu.

Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>

--
Mat Martineau
Intel

  reply	other threads:[~2021-04-30  0:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 14:59 [PATCH mptcp-next] mptcp: support SYSCTL only if enabled Matthieu Baerts
2021-04-30  0:07 ` Mat Martineau [this message]
2021-04-30 16:54   ` 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=9c92075-e759-baed-c1a5-7f167bfa60f9@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.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.