From: Jan Kara <jack@suse.cz>
To: linux-ext4@vger.kernel.org
Subject: SECRM, UNRM, COMPR flags
Date: Mon, 26 Sep 2016 11:11:49 +0200 [thread overview]
Message-ID: <20160926091149.GA7733@quack2.suse.cz> (raw)
Hi,
in ext4 we have these SECRM, UNRM, COMPR flags which users can set, they
can read them, but which actually don't do anything. This is actually
somewhat confusing - e.g. I've just got report about one tool which
apparently sets SECRM flag on a file in a hope that it is somehow safer.
Also this is a waste of flags.
I've checked other filesystems (xfs, btrfs) and they report EOPNOTSUPP if
these flags are not really supported. Should not we do the same in ext4? I
know there is a concern about breaking userspace but since other major
filesystems already behave this way I think there is a good chance tools
handle this reasonably... What do people thing?
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next reply other threads:[~2016-09-26 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 9:11 Jan Kara [this message]
2016-09-26 15:06 ` SECRM, UNRM, COMPR flags Theodore Ts'o
2016-09-27 8:35 ` Jan Kara
2016-09-27 11:45 ` Andreas Dilger
2016-09-28 23:30 ` Theodore Ts'o
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=20160926091149.GA7733@quack2.suse.cz \
--to=jack@suse.cz \
--cc=linux-ext4@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