public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Holmberg <Hans.Holmberg@wdc.com>
To: Carlos Maiolino <cem@kernel.org>
Cc: Dave Chinner <david@fromorbit.com>,
	"Darrick J . Wong" <djwong@kernel.org>, hch <hch@lst.de>,
	"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: allow ro mounts if rtdev or logdev are read-only
Date: Mon, 28 Apr 2025 11:51:24 +0000	[thread overview]
Message-ID: <8d4aa088-e59e-46bc-bc75-60eff2d49f4a@wdc.com> (raw)
In-Reply-To: <iboil7qz4s76y53wlwvpnu2diypdv5bdryoqwhlh4duat5dtj2@lkptlw2z3pdq>

On 28/04/2025 11:52, Carlos Maiolino wrote:
> On Fri, Apr 25, 2025 at 08:52:53AM +0000, Hans Holmberg wrote:
>> Allow read-only mounts on rtdevs and logdevs that are marked as
>> read-only and make sure those mounts can't be remounted read-write.
>>
>> Signed-off-by: Hans Holmberg <hans.holmberg@wdc.com>
>> ---
>>
>> I will post a couple of xfstests to add coverage for these cases.
>>
>>  fs/xfs/xfs_super.c | 24 +++++++++++++++++++++---
>>  1 file changed, 21 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xfs_super.c
>> index b2dd0c0bf509..d7ac1654bc80 100644
>> --- a/fs/xfs/xfs_super.c
>> +++ b/fs/xfs/xfs_super.c
>> @@ -380,10 +380,14 @@ xfs_blkdev_get(
>>  	struct file		**bdev_filep)
>>  {
>>  	int			error = 0;
>> +	blk_mode_t		mode;
>>
>> -	*bdev_filep = bdev_file_open_by_path(name,
>> -		BLK_OPEN_READ | BLK_OPEN_WRITE | BLK_OPEN_RESTRICT_WRITES,
>> -		mp->m_super, &fs_holder_ops);
>> +	mode = BLK_OPEN_READ | BLK_OPEN_RESTRICT_WRITES;
> 
> 	Does BLK_OPEN_RESTRICT_WRITES makes sense without BLK_OPEN_WRITE?
> 	Perhaps this should be OR'ed together with OPEN_WRITE below?

BLK_OPEN_RESTRICT_WRITES disallows other writers to mounted devs, and I
presume we want this for read-only mounts as well?

> 
> 
> -Carlos
> 
>> +	if (!xfs_is_readonly(mp))
>> +		mode |= BLK_OPEN_WRITE;
> 
>> +
>> +	*bdev_filep = bdev_file_open_by_path(name, mode,
>> +			mp->m_super, &fs_holder_ops);
>>  	if (IS_ERR(*bdev_filep)) {
>>  		error = PTR_ERR(*bdev_filep);
>>  		*bdev_filep = NULL;
>> @@ -1969,6 +1973,20 @@ xfs_remount_rw(
>>  	struct xfs_sb		*sbp = &mp->m_sb;
>>  	int error;
>>
>> +	if (mp->m_logdev_targp && mp->m_logdev_targp != mp->m_ddev_targp &&
>> +	    bdev_read_only(mp->m_logdev_targp->bt_bdev)) {
>> +		xfs_warn(mp,
>> +			"ro->rw transition prohibited by read-only logdev");
>> +		return -EACCES;
>> +	}
>> +
>> +	if (mp->m_rtdev_targp &&
>> +	    bdev_read_only(mp->m_rtdev_targp->bt_bdev)) {
>> +		xfs_warn(mp,
>> +			"ro->rw transition prohibited by read-only rtdev");
>> +		return -EACCES;
>> +	}
>> +
>>  	if (xfs_has_norecovery(mp)) {
>>  		xfs_warn(mp,
>>  			"ro->rw transition prohibited on norecovery mount");
>> --
>> 2.34.1
>>
> 


  reply	other threads:[~2025-04-28 11:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <M6FcYEJbADh29bAOdxfu6Qm-ktiyMPYZw39bsvsx-RJNJsTgTMpoahi2HA9UAqfEH9ueyBk3Kry5vydrxmxWrA==@protonmail.internalid>
2025-04-25  8:52 ` [PATCH] xfs: allow ro mounts if rtdev or logdev are read-only Hans Holmberg
2025-04-25 13:06   ` hch
2025-04-25 14:54   ` Darrick J. Wong
2025-04-28 12:27     ` Hans Holmberg
2025-04-28  9:52   ` Carlos Maiolino
2025-04-28 11:51     ` Hans Holmberg [this message]
2025-04-28 12:54       ` Carlos Maiolino
2025-04-28 13:04         ` hch
2025-04-29 11:58           ` Hans Holmberg

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=8d4aa088-e59e-46bc-bc75-60eff2d49f4a@wdc.com \
    --to=hans.holmberg@wdc.com \
    --cc=cem@kernel.org \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@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