From: Dan Carpenter <dan.carpenter@oracle.com>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: Colin King <colin.king@canonical.com>,
Christian Brauner <christian@brauner.io>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH][next] clone3: fix an unsigned args.cgroup comparison to less than zero
Date: Mon, 24 Feb 2020 10:31:57 +0300 [thread overview]
Message-ID: <20200224073157.GB3286@kadam> (raw)
In-Reply-To: <20200222121801.cu4dfnk4z5xd5uc2@wittgenstein>
On Sat, Feb 22, 2020 at 01:18:01PM +0100, Christian Brauner wrote:
> On Sat, Feb 22, 2020 at 12:15:13AM +0000, Colin King wrote:
> > From: Colin Ian King <colin.king@canonical.com>
> >
> > The less than zero comparison of args.cgroup is aways false because
> > args.cgroup is a u64 and can never be less than zero. I believe the
> > correct check is to cast args.cgroup to a s64 first to ensure an
> > invalid value is not copied to kargs->cgroup.
> >
> > Addresses-Coverity: ("Unsigned compared against 0")
> > Fixes: ef2c41cf38a7 ("clone3: allow spawning processes into cgroups")
> > Signed-off-by: Colin Ian King <colin.king@canonical.com>
>
> Thanks, Colin.
> Dan has reported this issue a few days prior on the janitors list so he
> likely should get a
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> too.
Colin found it independently so no need for a Reported-by.
> diff --git a/kernel/fork.c b/kernel/fork.c
> index 2diff --git a/kernel/fork.c b/kernel/fork.c
> index 2853e258fe1f..dca4dde3b5b2 100644
> --- a/kernel/fork.c
> +++ b/kernel/fork.c
> @@ -2618,7 +2618,8 @@ noinline static int copy_clone_args_from_user(struct kernel_clone_args *kargs,
> !valid_signal(args.exit_signal)))
> return -EINVAL;
>
> - if ((args.flags & CLONE_INTO_CGROUP) && args.cgroup < 0)
> + if ((args.flags & CLONE_INTO_CGROUP) &&
> + (args.cgroup > INT_MAX || (s64)args.cgroup < 0))
If we're capping it at INT_MAX then the check for negative isn't
required and static analysis tools know it's not so they might complain.
regards,
dan carpenter
next prev parent reply other threads:[~2020-02-24 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 0:15 [PATCH][next] clone3: fix an unsigned args.cgroup comparison to less than zero Colin King
2020-02-22 12:18 ` Christian Brauner
2020-02-24 7:31 ` Dan Carpenter [this message]
2020-02-24 12:25 ` Christian Brauner
2020-02-24 12:37 ` Dan Carpenter
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=20200224073157.GB3286@kadam \
--to=dan.carpenter@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=christian.brauner@ubuntu.com \
--cc=christian@brauner.io \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
/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