From: Serge Hallyn <serge.hallyn@canonical.com>
To: Chen Gang <gang.chen@asianux.com>
Cc: Cyrill Gorcunov <gorcunov@openvz.org>,
akpm@linux-foundation.org, keescook@chromium.org,
ebiederm@xmission.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
marcel@holtmann.org
Subject: Re: [PATCH] kernel: arg2 is unsigned long which is never < 0
Date: Wed, 6 Feb 2013 09:24:34 -0600 [thread overview]
Message-ID: <20130206152434.GB15220@sergelap> (raw)
In-Reply-To: <51123236.3060001@asianux.com>
Quoting Chen Gang (gang.chen@asianux.com):
> 于 2013年02月06日 16:56, Cyrill Gorcunov 写道:
> > On Wed, Feb 06, 2013 at 04:44:35PM +0800, Chen Gang wrote:
> >> >
> >> > diff --git a/kernel/sys.c b/kernel/sys.c
> >> > index 24d1ef5..568b9ca 100644
> >> > --- a/kernel/sys.c
> >> > +++ b/kernel/sys.c
> >> > @@ -2027,7 +2027,7 @@ SYSCALL_DEFINE5(prctl, int, option, unsigned long, arg2, unsigned long, arg3,
> >> > error = get_dumpable(me->mm);
> >> > break;
> >> > case PR_SET_DUMPABLE:
> >> > - if (arg2 < 0 || arg2 > 1) {
> >> > + if (arg2 > 1) {
> >> > error = -EINVAL;
> >> > break;
> >> > }
> > I guess
> >
> > if (arg2 != SUID_DUMPABLE_DISABLED &&
> > arg2 != SUID_DUMPABLE_ENABLED) {
> > error = -EINVAL;
> > break;
> > }
> >
> > would be better. Still, current patch looks good to me.
>
> thank you for your suggestion, firstly.
>
> and after read more, it seems a little more complex:
> for me, I think it would be better:
>
> if (arg2 != SUID_DUMP_DISABLE && arg2 != SUID_DUMP_USER) {
> error = -EINVAL;
> break;
> }
>
>
> the reason is below:
>
> it has 2 branches:
>
> branch 1:
>
> #define SUID_DUMP_DISABLE 0 /* No setuid dumping */
> #define SUID_DUMP_USER 1 /* Dump as user of process */
> #define SUID_DUMP_ROOT 2 /* Dump as root */
>
> in patch d6e711448137ca3301512cec41a2c2ce852b3d0a
> Signed-of-by Alan Cox in 2005.
> define these constant for using.
> change 2 choices to 3 choices (add a new choice).
>
> in patch abf75a5033d4da7b8a7e92321d74021d1fcfb502
> Signed-of-by Marcel Holtmann in 2006.
> find and fix a security issue for it.
>
>
> branch 2:
>
> #define SUID_DUMPABLE_DISABLED 0
> #define SUID_DUMPABLE_ENABLED 1
> #define SUID_DUMPABLE_SAFE 2
>
> in patch 54b501992dd2a839e94e76aa392c392b55080ce8
> Signed-of-by Kees Cook in Jul 30 2012
> define the constants for using
> print warning when detect unsafe core_pattern settings
>
> in patch 0f4cfb2e4e7a7e4e97a3e90e2ba1062f07fb2cb1
> Signed-of-by Oleg Nesterov in Oct 4 2012
> use SUID_DUMPABLE_ENABLED rather than hardcoded 1
>
> analysing:
> branch 1 and branch 2 have the same values with different macro names.
> branch 1 is much older than branch 2.
> for features:
> branch 1 is for functional feature and bug fix,
> branch 2 is for printing warning and beautifying code.
>
> it seems:
> branch 2 did not notice the branch 1, before it performs.
> if it noticed, it is meanless to define the new macros.
>
> result:
> still use the macros of branch 1
> and use branch 1 macros instead of branch 2 macros (need an additional patch).
>
> :-)
>
> Regards.
This really seems like splitting hairs to me.
Acked-by: Serge E. Hallyn <serge.hallyn@ubuntu.com>
on the original patch.
thanks,
-serge
next prev parent reply other threads:[~2013-02-06 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 8:44 [PATCH] kernel: arg2 is unsigned long which is never < 0 Chen Gang
2013-02-06 8:56 ` Cyrill Gorcunov
2013-02-06 10:36 ` Chen Gang
2013-02-06 15:24 ` Serge Hallyn [this message]
2013-02-07 1:54 ` Chen Gang
2013-02-06 15:35 ` Cyrill Gorcunov
2013-02-06 19:41 ` Kees Cook
2013-02-07 1:38 ` Chen Gang
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=20130206152434.GB15220@sergelap \
--to=serge.hallyn@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebiederm@xmission.com \
--cc=gang.chen@asianux.com \
--cc=gorcunov@openvz.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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