From: Hugo Mills <hugo@carfax.org.uk>
To: Josef Bacik <josef@toxicpanda.com>
Cc: Roman Mamedov <rm@romanrm.net>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] btrfs: do not allow -o compress-force to override per-inode settings
Date: Mon, 30 Nov 2020 15:04:09 +0000 [thread overview]
Message-ID: <20201130150409.GH1908@savella.carfax.org.uk> (raw)
In-Reply-To: <b92d0141-f68f-ce96-8099-e145ebc6f594@toxicpanda.com>
On Mon, Nov 30, 2020 at 09:50:13AM -0500, Josef Bacik wrote:
> On 11/30/20 9:08 AM, Roman Mamedov wrote:
> > On Mon, 30 Nov 2020 08:46:21 -0500
> > Josef Bacik <josef@toxicpanda.com> wrote:
> >
> > > However some time later we got chattr -c, which is a user way of
> > > indicating that the file shouldn't be compressed. This is at odds with
> > > -o compress-force. We should be honoring what the user wants, which is
> > > to disable compression.
> >
> > But chattr -c only removes the previously set chattr +c. There's no
> > "negative-c" to be forced by user in attributes. And +c is already unset on all
> > files by default. Unless I'm missing something? Thanks
> >
>
> The thing you're missing is that when we do chattr -c we're setting
> NOCOMPRESS on the file. The thing that I'm missing is what exactly we're
> trying to allow. If chattr -c is supposed to just be the removal of +c,
> then btrfs is doing the wrong thing by setting NOCOMPRESS. We also do the
> same thing when we clear a btrfs.compression property.
If I'm understanding this right, there's more than two states
here. There's a "default", and there's two "force" options -- forcing
nocompress, and forcing/allowing compression. If there's no c flag
set, the file could be in one of two states: default behaviour
(presumably defined by the value of the mount options), and
NOCOMPRESS. How do I tell which it is?
> I guess the question is what do we want? Do we want to only allow the user
> to indicate we want compression, or do we want to allow them to also
> indicate that they don't want compression? If we don't want to enable them
> to disable compression for a file, then this patch needs to be thrown away,
> but then we also need to fix up all the places we set NOCOMPRESS when we
> clear these flags. Thanks,
Hugo.
--
Hugo Mills | The last man on Earth sat in a room. Suddenly, there
hugo@... carfax.org.uk | was a knock at the door.
http://carfax.org.uk/ |
PGP: E2AB1DE4 | Frederic Brown
next prev parent reply other threads:[~2020-11-30 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 13:46 [PATCH] btrfs: do not allow -o compress-force to override per-inode settings Josef Bacik
2020-11-30 14:08 ` Roman Mamedov
2020-11-30 14:27 ` Amy Parker
2020-11-30 14:50 ` Josef Bacik
2020-11-30 15:01 ` Roman Mamedov
2020-11-30 15:10 ` Josef Bacik
2020-11-30 15:17 ` Roman Mamedov
2020-11-30 15:04 ` Hugo Mills [this message]
2020-11-30 15:12 ` Josef Bacik
2020-11-30 17:28 ` sys
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=20201130150409.GH1908@savella.carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.net \
/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