From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Andreas Dilger <adilger@sun.com>
Cc: cmm@us.ibm.com, tytso@mit.edu, sandeen@redhat.com,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] Add extent conversion support to chattr
Date: Fri, 12 Sep 2008 14:57:49 +0530 [thread overview]
Message-ID: <20080912092749.GC8405@skywalker> (raw)
In-Reply-To: <20080912091713.GY3086@webber.adilger.int>
On Fri, Sep 12, 2008 at 03:17:13AM -0600, Andreas Dilger wrote:
> On Sep 12, 2008 14:34 +0530, Aneesh Kumar wrote:
> > - _("Usage: %s [-RVf] [-+=AacDdijsSu] [-v version] files...\n"),
> > + _("Usage: %s [-RVf] [-+=AacDdijsSue] [-v version] files...\n"),
>
> Please keep options in alphabetical order.
>
> > @@ -105,6 +105,7 @@ static const struct flags_char flags_array[] = {
> > { EXT2_UNRM_FL, 'u' },
> > { EXT2_NOTAIL_FL, 't' },
> > { EXT2_TOPDIR_FL, 'T' },
> > + { EXT4_EXTENTS_FL, 'e'},
>
> I'd also prefer to keep these in alphabetical order, which they almost are.
>
> > @@ -199,7 +201,22 @@ static int change_attributes(const char * name)
> > if (set) {
> > + if (extent_file && !(sf & EXT4_EXTENTS_FL)) {
> > + if (!silent)
> > + com_err(program_name, 0,
> > + _("Clearing extent flag not supported on %s"),
> > + name);
> > + return -1;
> > + }
>
> Why not just try to set this flag and let the kernel decide what is
> possible?
>
The motivation is to give a clear message that we still don't support
clearing extent flags. If we pass it to the kernel we will get
operation not supported error which would confuse the user who does
chattr -de f1
-aneesh
next prev parent reply other threads:[~2008-09-12 9:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 9:04 [PATCH] Add extent conversion support to chattr Aneesh Kumar K.V
2008-09-12 9:17 ` Andreas Dilger
2008-09-12 9:27 ` Aneesh Kumar K.V [this message]
2008-09-12 15:26 ` Andreas Dilger
2008-09-12 9:31 ` Aneesh Kumar K.V
-- strict thread matches above, loose matches on Subject: below --
2008-09-09 9:12 Aneesh Kumar K.V
2008-09-09 11:46 ` Christoph Hellwig
2008-09-09 12:36 ` Aneesh Kumar K.V
2008-09-09 13:43 ` Theodore Tso
2008-09-09 14:09 ` Aneesh Kumar K.V
2008-09-09 14:39 ` Theodore Tso
2008-09-09 16:28 ` Aneesh Kumar K.V
2008-09-09 16:47 ` Theodore Tso
2008-09-09 16:50 ` Christoph Hellwig
2008-09-09 16:54 ` Theodore Tso
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=20080912092749.GC8405@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@sun.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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