All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Chase Venters <chase.venters@clientec.com>
Cc: Greg KH <gregkh@suse.de>,
	linux-kernel@vger.kernel.org, stable@kernel.org,
	torvalds@osdl.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Linux 2.6.17.4
Date: Fri, 07 Jul 2006 12:34:52 +0200	[thread overview]
Message-ID: <1152268492.3693.9.camel@localhost> (raw)
In-Reply-To: <200607061824.46990.chase.venters@clientec.com>

Hi Chase,

> >  		case PR_SET_DUMPABLE:
> > -			if (arg2 < 0 || arg2 > 2) {
> > +			if (arg2 < 0 || arg2 > 1) {
> >  				error = -EINVAL;
> >  				break;
> >  			}
> 
> Am I staring at this crooked, or not looking deep enough? My manual page for 
> prctl says 2 is valid there. Specifically:
> 
>               Since  kernel 2.6.13, the value 2 is also permitted; this causes
>               any binary which normally would not be dumped to be dumped read-
>               able   by   root   only.    (See   also   the   description   of
>               /proc/sys/fs/suid_dumpable in proc(5).)
> 
> ...has something changed, and my manpages don't reflect it? Did I miss a 
> conversation about this?

the manual page must change. This paragraph must be removed.

Regards

Marcel



      parent reply	other threads:[~2006-07-07 10:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06 22:27 Linux 2.6.17.4 Greg KH
2006-07-06 22:28 ` Greg KH
2006-07-06 22:43   ` Scott J. Harmon
2006-07-06 22:46     ` Greg KH
2006-07-06 22:54       ` Scott J. Harmon
2006-07-07  6:12         ` Jan Engelhardt
2006-07-06 23:49       ` Willy Tarreau
2006-07-06 23:53         ` [stable] " Greg KH
2006-07-06 23:56         ` Chris Wright
2006-07-06 23:57         ` Chase Venters
2006-07-06 23:24   ` Chase Venters
2006-07-06 23:54     ` [stable] " Greg KH
2006-07-07 10:34     ` Marcel Holtmann [this message]

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=1152268492.3693.9.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=akpm@osdl.org \
    --cc=chase.venters@clientec.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@osdl.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 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.