All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Oprala <ooprala@redhat.com>
To: selinux@tycho.nsa.gov
Subject: setfscreatecon optimizations
Date: Tue, 08 Jan 2013 14:20:50 +0100	[thread overview]
Message-ID: <50EC1D32.3090607@redhat.com> (raw)

Hi, there have been some attempts on the coreutils mailing list at 
optimizing cp copying by caching the selinux security context ( please 
see: http://lists.gnu.org/archive/html/coreutils/2013-01/msg00012.html ).
Would it be possible to perform some kind of caching inside 
setfscreatecon? For example not going through the whole process of 
setfscreatecon if the context to be set equals the current one?
Thanks,
Ondrej

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

             reply	other threads:[~2013-01-08 13:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 13:20 Ondrej Oprala [this message]
2013-01-08 14:48 ` setfscreatecon optimizations Stephen Smalley
2013-01-09 12:03   ` Ondrej Oprala
2013-01-09 14:30     ` Eric Paris
2013-01-09 14:51       ` Eric Paris
2013-01-09 20:17         ` Ondrej Oprala
2013-01-09 21:30           ` Daniel J Walsh

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=50EC1D32.3090607@redhat.com \
    --to=ooprala@redhat.com \
    --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.