From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: immutable (WORM) file system
Date: Tue, 13 Mar 2012 11:17:16 +1100 [thread overview]
Message-ID: <201203131117.16977.chris@csamuel.org> (raw)
In-Reply-To: <20120312234039.GA13695@twin.jikos.cz>
[-- Attachment #1: Type: Text/Plain, Size: 1817 bytes --]
On Tuesday 13 March 2012 10:40:39 David Sterba wrote:
> (I just know that the flag is there and is related to the question,
> haven't tested it myself and do not know what was the original
> intention.)
Not sure it helps, but the commits for these were:
commit fdebe2bd70047e057827cba85ba31b2545e31900
Author: Yan <yanzheng@21cn.com>
Date: Mon Jan 14 13:26:08 2008 -0500
Btrfs: Add readonly inode flag
This patch adds readonly inode flag support. A file with this flag
can't be modified, but can be deleted.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
and..
commit cb6db4e57632ba8589cc2f9fe1d0aa9116b87ab8
Author: Jeff Mahoney <jeffm@suse.de>
Date: Mon Aug 15 17:27:21 2011 +0000
Author: Jeff Mahoney <jeffm@suse.de>
Date: Mon Aug 15 17:27:21 2011 +0000
btrfs: btrfs_permission's RO check shouldn't apply to device nodes
This patch tightens the read-only access checks in btrfs_permission to
match the constraints in inode_permission. Currently, even though the
device node itself will be unmodified, read-write access to device nodes
is denied to when the device node resides on a read-only subvolume or a
is a file that has been marked read-only by the btrfs conversion utility.
With this patch applied, the check only affects regular files,
directories, and symlinks. It also restructures the code a bit so that
we don't duplicate the MAY_WRITE check for both tests.
Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
next prev parent reply other threads:[~2012-03-13 0:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 19:36 immutable (WORM) file system Fong Vang
2012-03-12 19:52 ` Chester
2012-03-13 0:09 ` Duncan
2012-03-12 23:40 ` David Sterba
2012-03-13 0:17 ` Chris Samuel [this message]
2012-03-14 11:58 ` João Eduardo Luís
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=201203131117.16977.chris@csamuel.org \
--to=chris@csamuel.org \
--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).