All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
	sds@epoch.ncsc.mil, chrisw@osdl.org
Subject: Re: [PATCH 1/4] vfs: adds the S_PRIVATE flag and adds use to security
Date: Sat, 05 Mar 2005 12:42:47 -0500	[thread overview]
Message-ID: <4229EF97.50403@suse.com> (raw)
In-Reply-To: <20050304212839.1d5aca4c.akpm@osdl.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andrew Morton wrote:
> Jeffrey Mahoney <jeffm@suse.com> wrote:
> 
>> This patch adds an S_PRIVATE flag to inode->i_flags to mark an inode as
>> filesystem-internal. As such, it should be excepted from the security
>> infrastructure to allow the filesystem to perform its own access control.
> 
> 
> OK, thanks.  I'll assume that the other three patches are unchanged.
> 
> I don't think we've heard from the SELinux team regarding these patches?
> 
> (See http://www.zip.com.au/~akpm/linux/patches/stuff/selinux-reiserfs/)

That's correct, the others are unchanged.

- -Jeff

- --
Jeff Mahoney
SuSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCKe+XLPWxlyuTD7IRApGeAJ9UWMIQSV1WlKlJg1Ml/hP36zSW0ACePTDW
qGUzKyItFVw9DFp9UoyaNHQ=
=LdAr
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-03-05 17:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 19:52 [PATCH 1/4] vfs: adds the S_PRIVATE flag and adds use to security Jeffrey Mahoney
2005-03-05  5:28 ` Andrew Morton
2005-03-05 17:42   ` Jeff Mahoney [this message]
2005-03-07 14:53   ` Stephen Smalley
2005-03-08  3:43   ` Chris Wright
  -- strict thread matches above, loose matches on Subject: below --
2005-03-01 15:37 Jeffrey Mahoney
2005-03-04  1:47 ` Jeff Mahoney

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=4229EF97.50403@suse.com \
    --to=jeffm@suse.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@epoch.ncsc.mil \
    --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.