All of lore.kernel.org
 help / color / mirror / Atom feed
From: liu weni <qingshenlwy@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: chris.mason@oracle.com, joel.becker@oracle.com, cjb@laptop.org,
	jmorris@namei.org, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, onlyflyer@gmail.com,
	strongzgy@gmail.com
Subject: Re: [PATCHv2 02/12]posix_acl: Add the check items
Date: Tue, 22 Dec 2009 22:31:38 +0800	[thread overview]
Message-ID: <b3657a100912220631n4d69ea66x23c1296e1abc468a@mail.gmail.com> (raw)
In-Reply-To: <20091222120803.GR18217@ZenIV.linux.org.uk>

Hi All:

    I'm sorry for my stupid. I am crazy for fixing this bug.
And make so much mistake.
Maybe I need cool down and think more.

--
Best Regards,
Liuwenyi
2009-12-22



2009/12/22 Al Viro <viro@zeniv.linux.org.uk>:
> On Mon, Dec 21, 2009 at 07:52:58PM +0800, Liuwenyi wrote:
>> @@ -102,12 +102,9 @@ static int btrfs_set_acl(struct btrfs_trans_han=
dle
>> *trans,
>> char *value =3D NULL;
>> mode_t mode;
>>
>> - if (acl) {
>> - ret =3D posix_acl_valid(acl);
>> - if (ret < 0)
>> - return ret;
>> - ret =3D 0;
>> - }
>> + ret =3D posix_acl_valid(acl);
>> + if (ret < 0)
>> + return ret;
>
> ... and now you can't remove acl from btrfs inode. =A0At all.
>
> NAK the entire series. =A0You are changing existing user-visible beha=
viour
> for all filesystems for no reason and at least in this case it's clea=
rly
> wrong change.
>

WARNING: multiple messages have this Message-ID (diff)
From: liu weni <qingshenlwy@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: chris.mason@oracle.com, joel.becker@oracle.com, cjb@laptop.org,
	jmorris@namei.org, linux-btrfs@vger.kernel.org,
	linux-kernel@vger.kernel.org, onlyflyer@gmail.com,
	strongzgy@gmail.com
Subject: Re: [PATCHv2 02/12]posix_acl: Add the check items
Date: Tue, 22 Dec 2009 22:31:38 +0800	[thread overview]
Message-ID: <b3657a100912220631n4d69ea66x23c1296e1abc468a@mail.gmail.com> (raw)
In-Reply-To: <20091222120803.GR18217@ZenIV.linux.org.uk>

Hi All:

    I'm sorry for my stupid. I am crazy for fixing this bug.
And make so much mistake.
Maybe I need cool down and think more.

--
Best Regards,
Liuwenyi
2009-12-22



2009/12/22 Al Viro <viro@zeniv.linux.org.uk>:
> On Mon, Dec 21, 2009 at 07:52:58PM +0800, Liuwenyi wrote:
>> @@ -102,12 +102,9 @@ static int btrfs_set_acl(struct btrfs_trans_handle
>> *trans,
>> char *value = NULL;
>> mode_t mode;
>>
>> - if (acl) {
>> - ret = posix_acl_valid(acl);
>> - if (ret < 0)
>> - return ret;
>> - ret = 0;
>> - }
>> + ret = posix_acl_valid(acl);
>> + if (ret < 0)
>> + return ret;
>
> ... and now you can't remove acl from btrfs inode.  At all.
>
> NAK the entire series.  You are changing existing user-visible behaviour
> for all filesystems for no reason and at least in this case it's clearly
> wrong change.
>

  reply	other threads:[~2009-12-22 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 11:52 [PATCHv2 02/12]posix_acl: Add the check items Liuwenyi
2009-12-21 11:52 ` Liuwenyi
2009-12-22 12:08 ` Al Viro
2009-12-22 14:31   ` liu weni [this message]
2009-12-22 14:31     ` liu weni
2009-12-22 14:48     ` Al Viro

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=b3657a100912220631n4d69ea66x23c1296e1abc468a@mail.gmail.com \
    --to=qingshenlwy@gmail.com \
    --cc=chris.mason@oracle.com \
    --cc=cjb@laptop.org \
    --cc=jmorris@namei.org \
    --cc=joel.becker@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=onlyflyer@gmail.com \
    --cc=strongzgy@gmail.com \
    --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 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.