From: "libaokun (A)" <libaokun1@huawei.com>
To: <mcgrof@kernel.org>, <keescook@chromium.org>, <yzaikin@google.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<yukuai3@huawei.com>, Hulk Robot <hulkci@huawei.com>,
Baokun Li <libaokun1@huawei.com>
Subject: Re: [PATCH -next] sysctl: returns -EINVAL when a negative value is passed to proc_doulongvec_minmax
Date: Tue, 14 Dec 2021 16:00:53 +0800 [thread overview]
Message-ID: <34f34475-2025-ebb5-7f2e-1a069fcc2a44@huawei.com> (raw)
In-Reply-To: <20211209085635.1288737-1-libaokun1@huawei.com>
在 2021/12/9 16:56, Baokun Li 写道:
> When we pass a negative value to the proc_doulongvec_minmax() function,
> the function returns 0, but the corresponding interface value does not
> change.
>
> we can easily reproduce this problem with the following commands:
> `cd /proc/sys/fs/epoll`
> `echo -1 > max_user_watches; echo $?; cat max_user_watches`
>
> This function requires a non-negative number to be passed in, so when
> a negative number is passed in, -EINVAL is returned.
>
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Baokun Li <libaokun1@huawei.com>
> ---
> kernel/sysctl.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index 7f07b058b180..537d2f75faa0 100644
> --- a/kernel/sysctl.c
> +++ b/kernel/sysctl.c
> @@ -1149,10 +1149,9 @@ static int __do_proc_doulongvec_minmax(void *data, struct ctl_table *table,
> sizeof(proc_wspace_sep), NULL);
> if (err)
> break;
> - if (neg)
> - continue;
> +
> val = convmul * val / convdiv;
> - if ((min && val < *min) || (max && val > *max)) {
> + if (neg || (min && val < *min) || (max && val > *max)) {
> err = -EINVAL;
> break;
> }
ping
next prev parent reply other threads:[~2021-12-14 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 8:56 Baokun Li
2021-12-14 8:00 ` libaokun (A) [this message]
2021-12-19 21:29 ` Luis Chamberlain
2021-12-20 8:53 ` libaokun (A)
2021-12-20 19:27 ` Luis Chamberlain
2021-12-21 1:15 ` libaokun (A)
2021-12-21 22:02 ` Luis Chamberlain
2021-12-22 1:26 ` libaokun (A)
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=34f34475-2025-ebb5-7f2e-1a069fcc2a44@huawei.com \
--to=libaokun1@huawei.com \
--cc=hulkci@huawei.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=yukuai3@huawei.com \
--cc=yzaikin@google.com \
/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
all inboxes | Powered by JetHome®