From: "Ernesto A. Fernández" <ernesto.mnd.fernandez@gmail.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, "Chris Mason" <clm@fb.com>,
"Josef Bacik" <jbacik@fb.com>, "David Sterba" <dsterba@suse.com>,
"Ernesto A. Fernández" <ernesto.mnd.fernandez@gmail.com>
Subject: Re: [PATCH] btrfs: preserve i_mode if __btrfs_set_acl() fails
Date: Sat, 29 Jul 2017 02:04:39 -0300 [thread overview]
Message-ID: <20170729050438.GA7465@debian.home> (raw)
In-Reply-To: <20170729004802.GA28703@li70-116.members.linode.com>
On Sat, Jul 29, 2017 at 12:48:04AM +0000, Josef Bacik wrote:
> On Fri, Jul 28, 2017 at 09:26:29PM -0300, Ernesto A. Fernández wrote:
> > + ret = __btrfs_set_acl(trans, inode, acl, type);
> > + if (ret)
> > + goto out;
> > +
> > + inode->i_mode = mode;
> > + inode_inc_iversion(inode);
> > + inode->i_ctime = current_time(inode);
> > + set_bit(BTRFS_INODE_COPY_EVERYTHING, &BTRFS_I(inode)->runtime_flags);
>
> This only needs to be set if we actually set the xattr. I'd fix setxattr to
> call it every time it's called.
I had not thought of that, thank you.
If I'm understanding this correctly the issue would be only when setting
a NULL default acl on an inode that is not a directory. In that case I
probably shouldn't be calling btrfs_update_inode either, but I can't move
that back to setxattr.
Perhaps __btrfs_set_acl could return an error in that case, like -ENOTDIR,
and then we can set ret back to 0 before returning from btrfs_set_acl.
> > + ret = btrfs_update_inode(trans, root, inode);
> > + BUG_ON(ret);
>
> No BUG_ON, return the error.
The call to BUG_ON was already there before my patch, only inside the
__btrfs_setxattr function. Since I didn't know the reason I thought it
was best not to change it. I'll do as you say in the next version.
Thank you for your review.
next prev parent reply other threads:[~2017-07-29 5:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-29 0:26 [PATCH] btrfs: preserve i_mode if __btrfs_set_acl() fails Ernesto A. Fernández
2017-07-29 0:48 ` Josef Bacik
2017-07-29 5:04 ` Ernesto A. Fernández [this message]
2017-07-30 2:18 ` [PATCH v2] " Ernesto A. Fernández
2017-08-02 6:18 ` [PATCH v3] " Ernesto A. Fernández
2017-08-14 16:05 ` David Sterba
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=20170729050438.GA7465@debian.home \
--to=ernesto.mnd.fernandez@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).