public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeffrey Mahoney <jeffm@suse.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: "Kevin O'Connor" <kevin@koconnor.net>,
	Chris Wright <chrisw@sous-sol.org>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, jgarzik@pobox.com,
	jmorris@namei.org
Subject: Re: Size-128 slab leak
Date: Mon, 13 Feb 2006 23:52:45 -0500	[thread overview]
Message-ID: <43F1621D.1060401@suse.com> (raw)
In-Reply-To: <1138972872.18268.327.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> BTW, Jeff - I assume you know about the unrelated breakage in
> SELinux/reiserfs support that was introduced by the changes for atomic
> security labeling of inodes in 2.6.14.  If you care, you might want to
> use the same workaround upstreamed for xfs for 2.6.16.  But I understand
> that SELinux is not a priority in SuSE presently.

Hi Stephen -

Thanks for the reminder on this one. I have a series of patches that
rework the reiserfs xattr implementation. One of the patches adds
journalling for xattrs, including putting the inherited ACLs in the same
transaction as the object creation. Adding the SELinux attribute to the
same transaction wouldn't be too much of a problem.

I should have a patch tomorrow, though it will depend on the xattr patchset.

-Jeff

--
Jeff Mahoney
SUSE Labs

      parent reply	other threads:[~2006-02-14  4:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31  2:49 Size-128 slab leak Kevin O'Connor
2006-02-02  7:10 ` Andrew Morton
2006-02-02  7:32   ` Pekka Enberg
2006-02-03  6:21     ` Manfred Spraul
2006-02-03  4:00   ` Kevin O'Connor
2006-02-03 13:21     ` Stephen Smalley
2006-02-03 15:13       ` James Morris
2006-02-04  1:13       ` Kevin O'Connor
2006-02-14  4:52       ` Jeffrey Mahoney [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=43F1621D.1060401@suse.com \
    --to=jeffm@suse.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@sous-sol.org \
    --cc=jgarzik@pobox.com \
    --cc=jmorris@namei.org \
    --cc=kevin@koconnor.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@epoch.ncsc.mil \
    /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