[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHuHWtnbVsS2pp5EySmZ_72fCrDqKJTAOkssa-D-X5wKoR9uWQ@mail.gmail.com>
Date: Tue, 6 Dec 2022 10:42:03 +0800
From: Chung-Chiang Cheng <shepjeng@...il.com>
To: Filipe Manana <fdmanana@...nel.org>
Cc: Chung-Chiang Cheng <cccheng@...ology.com>, clm@...com,
josef@...icpanda.com, dsterba@...e.com,
linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel@...heng.net, Johnny Chang <johnnyc@...ology.com>
Subject: Re: [PATCH] btrfs: refuse to remount read-write with unsupported
compat-ro features
On Mon, Dec 5, 2022 at 6:45 PM Filipe Manana <fdmanana@...nel.org> wrote:
>
> Wasn't this already done by the following commit?
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=81d5d61454c365718655cfc87d8200c84e25d596
>
> Thanks.
>
Wow. I did not notice this commit doing the same job by Qu. But I have
tested the latest linux-6.1 rc-7, and it's still able to mount a unsupported
comat-ro btrfs as read-write via remount.
It's caused by the follow-up commit d7f67ac9a928 ("btrfs: relax
block-group-tree feature dependency checks"). This commit checks read-
only with the current superblock, which will always pass in the situation
remounting from read-only to read-write. It seems `btrfs_check_features()`
cannot cover this scenario.
if (compat_ro_unsupp && !sb_rdonly(sb)) {
^^^^^^^^^^^^^^
Thanks,
C.C.Cheng
Powered by blists - more mailing lists