All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: selinux@tycho.nsa.gov
Cc: Eric Paris <eparis@redhat.com>, Stephen Smalley <sds@tycho.nsa.gov>
Subject: [PATCH][RFC] Unify printk messgaes
Date: Tue, 26 Feb 2008 20:53:52 +1100 (EST)	[thread overview]
Message-ID: <Xine.LNX.4.64.0802262049370.10387@us.intercode.com.au> (raw)

I noticed that we had a mix of "SELinux:" and "security:" prefixes in our 
kernel boot messages, so I've unified these to "SELinux:" with the patch 
below to reduce user confusion.  (It doesn't try and fix every printk, 
just the ones with "security:").

Also simplified the avtab hash message, from:

  SELinux:8192 avtab hash slots allocated. Num of rules:163922

to

  SELinux: 8192 avtab hash slots, 163922 rules.


Comments?

---

             reply	other threads:[~2008-02-26  9:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26  9:53 James Morris [this message]
2008-02-26 12:36 ` [PATCH][RFC] Unify printk messgaes Stephen Smalley
2008-02-26 13:39   ` James Morris
2008-02-26 15:08   ` Christopher J. PeBenito
2008-02-26 17:23     ` Stephen Smalley
2008-02-26 22:08   ` Russell Coker
2008-02-26 13:48 ` Eric Paris
2008-02-26 14:04   ` 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=Xine.LNX.4.64.0802262049370.10387@us.intercode.com.au \
    --to=jmorris@namei.org \
    --cc=eparis@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    /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.