-------- Original Message --------
Subject: Re: [RFC PATCH] Revert "btrfs: allow mounting btrfs subvolumes
with different ro/rw options"
From: Goffredo Baroncelli <[email protected]>
To: Qu Wenruo <[email protected]>, [email protected]
Date: 2014年07月03日 01:48
On 07/01/2014 11:30 AM, Qu Wenruo wrote:
This commit has the following problem:
1) Break the ro mount rule.
When users mount the whole btrfs ro, it is still possible to mount
subvol rw and change the contents. Which make the whole fs ro mount
non-sense.
Where is the problem ? I see an use case when I want a conservative default:
mount all ro except some subvolumes.
In any case it is not a security problem because if the user has the capability
to mount a subvolume, also he has the capability to remount,rw the whole
filesystem.
Not security problem but behavior not consistent.
If user mount the whole disk ro, he or she want the fs read only and
nothing will change in it.
If you mount a subvol rw, then the whole disk ro expectation is broken.
Things will change even the whole
disk is readonly.
The problem also happens when a parent subvol is mounted rw but child
subvol is mounted ro.
User can still modify the child subvol through parent subvol, still
broke the readonly rule.
Thanks,
Qu
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
