From: Adam Borowski <kilobyte@angband.pl>
To: dsterba@suse.cz, Mark Fasheh <mfasheh@suse.de>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH resend 1/2] btrfs: allow defrag on a file opened ro that has rw permissions
Date: Tue, 24 Jul 2018 22:35:28 +0200 [thread overview]
Message-ID: <20180724203528.mr4exunw5ivjk7d7@angband.pl> (raw)
In-Reply-To: <20180723152624.GO26141@twin.jikos.cz>
On Mon, Jul 23, 2018 at 05:26:24PM +0200, David Sterba wrote:
> On Wed, Jul 18, 2018 at 12:08:59AM +0200, Adam Borowski wrote:
(Combined with as-folded)
| | btrfs: allow defrag on a file opened read-only that has rw permissions
| |
> > Requiring a rw descriptor conflicts both ways with exec, returning ETXTBSY
> > whenever you try to defrag a program that's currently being run, or
> > causing intermittent exec failures on a live system being defragged.
> >
> > As defrag doesn't change the file's contents in any way, there's no reason
> > to consider it a rw operation. Thus, let's check only whether the file
> > could have been opened rw. Such access control is still needed as
> > currently defrag can use extra disk space, and might trigger bugs.
<-----
| | We give EINVAL when the request is invalid; here it's ok but merely the
| | user has insufficient privileges. Thus, this return value reflects the
| | error better -- as discussed in the identical case for dedupe.
| |
| | According to codesearch.debian.net, no userspace program distinguishes
| | these values beyond strerror().
| |
| | Signed-off-by: Adam Borowski <kilobyte@angband.pl>
| | Reviewed-by: David Sterba <dsterba@suse.com>
| | [ fold the EPERM patch from Adam ]
| | Signed-off-by: David Sterba <dsterba@suse.com>
[...]
> So, I'll add the patch to 4.19 queue. It's small and isolated change so
> a revert would be easy in case we find something bad. The 2nd patch
> should be IMHO part of this change as it's logical to return the error
> code in the patch that modifies the user visible behaviour.
A nitpick: the new commit message has a dangling pointer "this" to the title
of the commit that was squashed. It was:
| btrfs: defrag: return EPERM not EINVAL when only permissions fail
It'd be nice if it could be inserted in some form in the place I marked with
an arrow.
But then, commit messages are not vital. The actual functionality patch has
been applied correctly. And thanks for adding the comment.
Meow!
--
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets. Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable And Non-Discriminatory prices.
next prev parent reply other threads:[~2018-07-24 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 22:05 [PATCH resend 0/2] btrfs: fix races between exec and defrag Adam Borowski
2018-07-17 22:08 ` [PATCH resend 1/2] btrfs: allow defrag on a file opened ro that has rw permissions Adam Borowski
2018-07-17 22:09 ` [PATCH resend 2/2] btrfs: defrag: return EPERM not EINVAL when only permissions fail Adam Borowski
2018-07-23 15:26 ` [PATCH resend 1/2] btrfs: allow defrag on a file opened ro that has rw permissions David Sterba
2018-07-24 20:35 ` Adam Borowski [this message]
2018-08-01 13:03 ` 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=20180724203528.mr4exunw5ivjk7d7@angband.pl \
--to=kilobyte@angband.pl \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfasheh@suse.de \
/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).