public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marco Stornelli <marco.stornelli@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	viro@zeniv.linux.org.uk, Andi Kleen <ak@linux.intel.com>,
	tytso@mit.edu
Subject: Re: [PATCH 2/4] EXT4: Set NOSEC flag early when there are no xattrs
Date: Sat, 28 May 2011 11:08:01 +0200	[thread overview]
Message-ID: <4DE0BB71.9000303@gmail.com> (raw)
In-Reply-To: <1306536845-24162-2-git-send-email-andi@firstfloor.org>

Il 28/05/2011 00:54, Andi Kleen ha scritto:
> From: Andi Kleen<ak@linux.intel.com>
>
> This avoids a xattr lookup on every write.
>
> Cc: tytso@mit.edu
> Signed-off-by: Andi Kleen<ak@linux.intel.com>

Are ext2/3 affected too? It seems to me that more or less the xattr 
management for the extN series is the same, isn't it?

Marco

  reply	other threads:[~2011-05-28  9:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27 22:54 [PATCH 1/4] Cache xattr security drop check for write Andi Kleen
2011-05-27 22:54 ` [PATCH 2/4] EXT4: Set NOSEC flag early when there are no xattrs Andi Kleen
2011-05-28  9:08   ` Marco Stornelli [this message]
2011-05-28 11:24     ` Chris Mason
2011-05-28 14:43     ` Andi Kleen
2011-05-27 22:54 ` [PATCH 3/4] BTRFS: Set NOSEC early for btrfs Andi Kleen
2011-05-27 22:54 ` [PATCH 4/4] XFS: Set NOSEC flag early when inode has no xattrs Andi Kleen
2011-05-28 11:42 ` [PATCH 1/4] Cache xattr security drop check for write Al Viro
2011-05-29 13:52 ` Valdis.Kletnieks
2011-05-29 14:24   ` Andi Kleen
2011-05-29 17:48     ` Valdis.Kletnieks

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=4DE0BB71.9000303@gmail.com \
    --to=marco.stornelli@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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