From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] remove CONFIG_XFS_SECURITY
Date: Mon, 7 Jan 2008 07:12:09 +0000 [thread overview]
Message-ID: <20080107071208.GA29713@infradead.org> (raw)
In-Reply-To: <47819E47.4030906@sandeen.net>
On Sun, Jan 06, 2008 at 09:36:39PM -0600, Eric Sandeen wrote:
> Is there any point to this option? Sure, it disables the ability
> to set security attributes at runtime, but it doesn't slim down
> any code.
>
> Any reason to not remove it, and always allow security attributes
> to be set?
I suspect the reason it is there currently is because the other
filesystems have similar option. Removing it sounds perfectly
fine to me.
next prev parent reply other threads:[~2008-01-07 7:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 3:36 [PATCH] remove CONFIG_XFS_SECURITY Eric Sandeen
2008-01-07 7:12 ` Christoph Hellwig [this message]
2008-02-20 0:42 ` Eric Sandeen
2008-04-07 2:23 ` Timothy Shimmin
2008-04-11 14:39 ` [PATCH V2] " Eric Sandeen
2008-04-11 16:04 ` Christoph Hellwig
2008-04-11 16:13 ` Eric Sandeen
2008-04-15 0:33 ` Timothy Shimmin
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=20080107071208.GA29713@infradead.org \
--to=hch@infradead.org \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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