From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>,
fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: do not allow trimming when a fs is mounted with the nologreplay option
Date: Tue, 26 Mar 2019 21:40:08 +0800 [thread overview]
Message-ID: <dbf7aa7b-3ea8-e5da-eb8f-746cbc5e4487@gmx.com> (raw)
In-Reply-To: <d828e591-22f6-faf2-76ec-1f52397ba858@suse.com>
On 2019/3/26 下午8:17, Nikolay Borisov wrote:
>
>
> On 26.03.19 г. 12:49 ч., fdmanana@kernel.org wrote:
>> From: Filipe Manana <fdmanana@suse.com>
>>
>> Whan a filesystem is mounted with the nologreplay mount option, which
>> requires it to be mounted in RO mode as well, we can not allow discard on
>> free space inside block groups, because log trees refer to extents that
>> are not pinned in a block group's free space cache (pinning the extents is
>> precisely the first phase of replaying a log tree).
>>
>> So do not allow the fitrim ioctl to do anything when the filesystem is
>> mounted with the nologreplay option, because later it can be mounted RW
>> without that option, which causes log replay to happen and result in
>> either a failure to replay the log trees (leading to a mount failure), a
>> crash or some silent corruption.
>>
>> Reported-by: Darrick J. Wong <darrick.wong@oracle.com>
>> Signed-off-by: Filipe Manana <fdmanana@suse.com>
>
> Does it make sense to make the check a bit more specific and only return
> EROFS when NOLOGREPLAY and the log tree has non-null generation?
To me fstrim is a WRITE operation, why it is allowed even in RO mount?
Thanks,
Qu
>
> In any case:
>
> Reviewed-by: Nikolay Borisov <nborisov@suse.com>
>
>> ---
>> fs/btrfs/ioctl.c | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
>> index 494f0f10d70e..01808934d21f 100644
>> --- a/fs/btrfs/ioctl.c
>> +++ b/fs/btrfs/ioctl.c
>> @@ -501,6 +501,16 @@ static noinline int btrfs_ioctl_fitrim(struct file *file, void __user *arg)
>> if (!capable(CAP_SYS_ADMIN))
>> return -EPERM;
>>
>> + /*
>> + * If the fs is mounted with nologreplay, which requires it to be
>> + * mounted in RO mode as well, we can not allow discard on free space
>> + * inside block groups, because log trees refer to extents that are not
>> + * pinned in a block group's free space cache (pinning the extents is
>> + * precisely the first phase of replaying a log tree).
>> + */
>> + if (btrfs_test_opt(fs_info, NOLOGREPLAY))
>> + return -EROFS;
>> +
>> rcu_read_lock();
>> list_for_each_entry_rcu(device, &fs_info->fs_devices->devices,
>> dev_list) {
>>
next prev parent reply other threads:[~2019-03-26 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 10:49 [PATCH] Btrfs: do not allow trimming when a fs is mounted with the nologreplay option fdmanana
2019-03-26 12:17 ` Nikolay Borisov
2019-03-26 12:35 ` Filipe Manana
2019-03-26 12:39 ` Nikolay Borisov
2019-03-28 15:54 ` David Sterba
2019-03-26 13:40 ` Qu Wenruo [this message]
2019-03-26 13:48 ` David Sterba
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=dbf7aa7b-3ea8-e5da-eb8f-746cbc5e4487@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.