linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: James Morris <jmorris@namei.org>,
	Kees Cook <kees.cook@canonical.com>,
	Alex Riesen <raa.lkml@gmail.com>,
	Casey Schaufler <casey@schaufler-ca.com>,
	linux-security-module@vger.kernel.org,
	David Howells <dhowells@redhat.com>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Simon Kagstrom <simon.kagstrom@netinsight.net>,
	David Woodhouse <David.Woodhouse@intel.com>,
	Robin Getz <rgetz@analog.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Paul Moore <paul.moore@hp.com>,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Etienne Basset <etienne.basset@numericable.fr>,
	"David P. Quigley" <dpquigl@tycho.nsa.gov>,
	LKLM <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] syslog: distinguish between /proc/kmsg and syscalls
Date: Thu, 04 Feb 2010 16:49:12 -0500	[thread overview]
Message-ID: <1265320152.5447.17.camel@localhost> (raw)
In-Reply-To: <20100204213106.GB25497@us.ibm.com>

On Thu, 2010-02-04 at 15:31 -0600, Serge E. Hallyn wrote:
> Quoting James Morris (jmorris@namei.org):
> > On Thu, 4 Feb 2010, Kees Cook wrote:
> > 
> > > Hi Alex,
> > > 
> > > On Thu, Feb 04, 2010 at 08:58:43AM +0100, Alex Riesen wrote:
> > > > > +       /* /proc/kmsg can open be opened by CAP_SYS_ADMIN */
> > > > > +       if (type != 1 && from_file)
> > > > > +               return 0;
> > > > 
> > > > "can open be opened"?
> > > 
> > > Erk, sorry.  s/open //
> > > 
> > > James, do you want a patch for that?
> > 
> > I guess... and 'opened with' might be better.
> 
> I'd still as mentioned yesterday prefer "requires CAP_SYS_ADMIN to open"
> Otherwise, every time I see the comment I expect stricter requirements,
> not laxer ones, on the other actions.  However, I think with the second
> patch switching 1 for a meaningful name, the comment isn't even necessary
> or noticable any more.

Agreed, the names make the function understandable, the comment confused
the mess out of me.


  reply	other threads:[~2010-02-04 21:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02  5:53 [PATCH] syslog: distinguish between /proc/kmsg and syscalls Kees Cook
2010-02-02  6:15 ` Casey Schaufler
2010-02-02 20:20   ` Kees Cook
2010-02-02 21:25     ` Serge E. Hallyn
2010-02-02 21:59       ` James Morris
2010-02-03 19:15         ` [PATCH 1/2] " Kees Cook
2010-02-03 20:44           ` Serge E. Hallyn
2010-02-03 19:23         ` [PATCH 2/2] syslog: use defined constants instead of raw numbers Kees Cook
2010-02-03 20:47           ` Serge E. Hallyn
2010-02-03 23:36         ` [PATCH v2 1/2] syslog: distinguish between /proc/kmsg and syscalls Kees Cook
2010-02-04  0:30           ` Serge E. Hallyn
2010-02-04  1:39             ` John Johansen
2010-02-04  3:52           ` James Morris
2010-02-04  7:58           ` Alex Riesen
2010-02-04  8:09             ` Kees Cook
2010-02-04 21:17               ` James Morris
2010-02-04 21:31                 ` Serge E. Hallyn
2010-02-04 21:49                   ` Eric Paris [this message]
2010-02-03 23:37         ` [PATCH v2 2/2] syslog: use defined constants instead of raw numbers Kees Cook
2010-02-04  0:35           ` Serge E. Hallyn
2010-02-04  1:38           ` John Johansen
2010-02-04  3:51           ` James Morris

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=1265320152.5447.17.camel@localhost \
    --to=eparis@redhat.com \
    --cc=David.Woodhouse@intel.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=casey@schaufler-ca.com \
    --cc=dhowells@redhat.com \
    --cc=dpquigl@tycho.nsa.gov \
    --cc=etienne.basset@numericable.fr \
    --cc=gregkh@suse.de \
    --cc=jmorris@namei.org \
    --cc=kees.cook@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paul.moore@hp.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=raa.lkml@gmail.com \
    --cc=rgetz@analog.com \
    --cc=sds@tycho.nsa.gov \
    --cc=serue@us.ibm.com \
    --cc=simon.kagstrom@netinsight.net \
    /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;
as well as URLs for NNTP newsgroup(s).