public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge.hallyn@canonical.com>
To: Kees Cook <kees.cook@canonical.com>
Cc: Paul Bolle <pebolle@tiscali.nl>,
	linux-kernel@vger.kernel.org,
	David Woodhouse <dwmw2@infradead.org>,
	Arnd Bergmann <arnd@arndb.de>,
	mtk.manpages@gmail.com, Serge Hallyn <serge.hallyn@canonical.com>
Subject: Re: [PATCH v2 2/2] man-pages: SYSLOG_ACTION_* constants are now exported
Date: Tue, 8 Feb 2011 21:26:21 -0600	[thread overview]
Message-ID: <20110209032621.GA28107@localhost> (raw)
In-Reply-To: <20110208223251.GP1457@outflux.net>

Quoting Kees Cook (kees.cook@canonical.com):
> On Tue, Feb 08, 2011 at 11:15:34PM +0100, Paul Bolle wrote:
> > The kernel now exports <linux/syslog.h>. This makes the SYSLOG_ACTION_*
> > constants available to userspace. This allows to replace the magic
> > numbers used in this man page with (what should be) more descriptive
> > names. The quote form kernel/printk.c can now also be dropped.
> > 
> > A few (more or less related) things were also fixed or changed:
> > - add a new sub section "The command types";
> > - the (userspace) buffer is called bufp everywhere (and not buf);
> > - add some whitespace to all call descriptions;
> > - use "ignored" in some call descriptions (instead of "dummy").
> > 
> > Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> 
> Acked-by: Kees Cook <kees.cook@canonical.com>
> 
> 
> As an aside, it might be a good idea to send an additional patch (since
> it's logically separate from this) to update this portion of the man-page:
> 
>    EPERM  An attempt was made to change console_loglevel or clear the
>           kernel message ring buffer by a process without  sufficient
>           privi lege (more precisely: without the CAP_SYS_ADMIN capability).
> 
> At least s/CAP_SYS_ADMIN/CAP_SYSLOG/, but probably include details about
> which options are considered privileged.
> 
> Though that should probably go with including the description of CAP_SYSLOG
> in the "capabilities" man-page.

Thanks for the reminder, Kees.  Michael, I'll try to get an update for
capabilities.7 to you soon.

-serge

      reply	other threads:[~2011-02-09  3:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 22:15 [PATCH v2 2/2] man-pages: SYSLOG_ACTION_* constants are now exported Paul Bolle
2011-02-08 22:32 ` Kees Cook
2011-02-09  3:26   ` Serge E. Hallyn [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=20110209032621.GA28107@localhost \
    --to=serge.hallyn@canonical.com \
    --cc=arnd@arndb.de \
    --cc=dwmw2@infradead.org \
    --cc=kees.cook@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=pebolle@tiscali.nl \
    /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