From: Matthieu Baerts <matttbe@kernel.org>
To: Gregory Detal <gregory.detal@gmail.com>,
MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next 1/2] mptcp: only allow set existing scheduler for net.mptcp.scheduler
Date: Tue, 30 Apr 2024 16:00:20 +0200 [thread overview]
Message-ID: <45081e80-632a-40a2-b059-0ee00d624f36@kernel.org> (raw)
In-Reply-To: <20240430-sysctl_scheduler-v1-1-8187148850df@gmail.com>
On 30/04/2024 14:06, Gregory Detal wrote:
> The current behavior is to accept any strings as inputs, this results in
> an inconsistent result where an unexisting scheduler can be set:
>
> # sysctl -w net.mptcp.scheduler=notdefault
> net.mptcp.scheduler = notdefault
>
> This patch changes this behavior by checking for existing scheduler
> before accepting the input.
>
> Fixes: e3b2870b6d22 ("mptcp: add a new sysctl scheduler")
> Signed-off-by: Gregory Detal <gregory.detal@gmail.com>
> ---
> net/mptcp/ctrl.c | 40 +++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 39 insertions(+), 1 deletion(-)
>
> diff --git a/net/mptcp/ctrl.c b/net/mptcp/ctrl.c
> index 8d661156ab8c..0e69bd0ea302 100644
> --- a/net/mptcp/ctrl.c
> +++ b/net/mptcp/ctrl.c
> @@ -96,6 +96,44 @@ static void mptcp_pernet_set_defaults(struct mptcp_pernet *pernet)
> }
>
> #ifdef CONFIG_SYSCTL
> +
We can remove this extra new line here: I can do that when applying the
patches if I don't forget.
> +static int mptcp_set_scheduler(const struct net *net, const char *name)
(...)
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
next prev parent reply other threads:[~2024-04-30 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 12:06 [PATCH mptcp-next 0/2] mptcp: fix net.mptcp.scheduler behavior Gregory Detal
2024-04-30 12:06 ` [PATCH mptcp-next 1/2] mptcp: only allow set existing scheduler for net.mptcp.scheduler Gregory Detal
2024-04-30 14:00 ` Matthieu Baerts [this message]
2024-04-30 12:06 ` [PATCH mptcp-next 2/2] mptcp: add net.mptcp.available_schedulers Gregory Detal
2024-04-30 12:59 ` [PATCH mptcp-next 0/2] mptcp: fix net.mptcp.scheduler behavior MPTCP CI
2024-04-30 14:00 ` Matthieu Baerts
2024-04-30 14:00 ` Matthieu Baerts
2024-05-02 14:16 ` Geliang Tang
2024-05-03 1:04 ` Mat Martineau
2024-05-03 16:45 ` 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=45081e80-632a-40a2-b059-0ee00d624f36@kernel.org \
--to=matttbe@kernel.org \
--cc=gregory.detal@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox