linux-ext4 - Re: Ideas on unified real-ro mount option across all filesystems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 17 Dec 2015 09:58:32 +0800
From:	Qu Wenruo <quwenruo@...fujitsu.com>
To:	fsdevel <linux-fsdevel@...r.kernel.org>
CC:	btrfs <linux-btrfs@...r.kernel.org>, <linux-ext4@...r.kernel.org>,
	<linux-xfs@...r.kernel.org>
Subject: Re: Ideas on unified real-ro mount option across all filesystems

And here is the existing discussion in btrfs mail list, just for reference:

http://thread.gmane.org/gmane.comp.file-systems.btrfs/51098

Thanks,
Qu

Qu Wenruo wrote on 2015/12/17 09:41 +0800:
> Hi,
>
> In a recent btrfs patch, it is going to add a mount option to disable
> log replay for btrfs, just like "norecovery" for ext4/xfs.
>
> But in the discussion on the mount option name and use case, it seems
> better to have an unified and fs independent mount option alias for real
> RO mount
>
> Reasons:
> 1) Some file system may have already used [no]"recovery" mount option
>     In fact, btrfs has already used "recovery" mount option.
>     Using "norecovery" mount option will be quite confusing for btrfs.
>
> 2) More straight forward mount option
>     Currently, to get real RO mount, for ext4/xfs, user must use -o
>     ro,norecovery.
>     Just ro won't ensure real RO, and norecovery can't be used alone.
>     If we have a simple alias, it would be much better for user to use.
>     (it maybe done just in user space mount)
>
>     Not to mention some fs (yeah, btrfs again) doesn't have "norecovery"
>     but "nologreplay".
>
> 3) A lot of user even don't now mount ro can still modify device
>     Yes, I didn't know this point until I checked the log replay code of
>     btrfs.
>     Adding such mount option alias may raise some attention of users.
>
>
> Any ideas about this?
>
> Thanks,
> Qu
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html