All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chandan Babu R <chandan.babu@oracle.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org, cem@kernel.org
Subject: Re: [PATCH V2 12/23] xfs_db: Add support to read from external log device
Date: Thu, 13 Jul 2023 10:54:26 +0530	[thread overview]
Message-ID: <87a5w0jouy.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <20230712173529.GK108251@frogsfrogsfrogs>

On Wed, Jul 12, 2023 at 10:35:29 AM -0700, Darrick J. Wong wrote:
> On Tue, Jun 06, 2023 at 02:57:55PM +0530, Chandan Babu R wrote:
>> This commit introduces a new function set_log_cur() allowing xfs_db to read
>> from an external log device. This is required by a future commit which will
>> add the ability to dump metadata from external log devices.
>> 
>> Signed-off-by: Chandan Babu R <chandan.babu@oracle.com>
>> ---
>>  db/io.c | 57 ++++++++++++++++++++++++++++++++++++++++++++-------------
>>  1 file changed, 44 insertions(+), 13 deletions(-)
>> 
>> diff --git a/db/io.c b/db/io.c
>> index 3d257236..a6feaba3 100644
>> --- a/db/io.c
>> +++ b/db/io.c
>> @@ -508,18 +508,19 @@ write_cur(void)
>>  
>>  }
>>  
>> -void
>> -set_cur(
>> -	const typ_t	*type,
>> -	xfs_daddr_t	blknum,
>> -	int		len,
>> -	int		ring_flag,
>> -	bbmap_t		*bbmap)
>> +static void
>> +__set_cur(
>> +	struct xfs_buftarg	*btargp,
>> +	const typ_t		*type,
>> +	xfs_daddr_t		 blknum,
>> +	int			 len,
>> +	int			 ring_flag,
>> +	bbmap_t			*bbmap)
>>  {
>> -	struct xfs_buf	*bp;
>> -	xfs_ino_t	dirino;
>> -	xfs_ino_t	ino;
>> -	uint16_t	mode;
>> +	struct xfs_buf		*bp;
>> +	xfs_ino_t		dirino;
>> +	xfs_ino_t		ino;
>> +	uint16_t		mode;
>>  	const struct xfs_buf_ops *ops = type ? type->bops : NULL;
>>  	int		error;
>>  
>> @@ -548,11 +549,11 @@ set_cur(
>>  		if (!iocur_top->bbmap)
>>  			return;
>>  		memcpy(iocur_top->bbmap, bbmap, sizeof(struct bbmap));
>> -		error = -libxfs_buf_read_map(mp->m_ddev_targp, bbmap->b,
>> +		error = -libxfs_buf_read_map(btargp, bbmap->b,
>>  				bbmap->nmaps, LIBXFS_READBUF_SALVAGE, &bp,
>>  				ops);
>>  	} else {
>> -		error = -libxfs_buf_read(mp->m_ddev_targp, blknum, len,
>> +		error = -libxfs_buf_read(btargp, blknum, len,
>>  				LIBXFS_READBUF_SALVAGE, &bp, ops);
>>  		iocur_top->bbmap = NULL;
>>  	}
>> @@ -589,6 +590,36 @@ set_cur(
>>  		ring_add();
>>  }
>>  
>> +void
>> +set_cur(
>> +	const typ_t	*type,
>> +	xfs_daddr_t	blknum,
>> +	int		len,
>> +	int		ring_flag,
>> +	bbmap_t		*bbmap)
>> +{
>> +	__set_cur(mp->m_ddev_targp, type, blknum, len, ring_flag, bbmap);
>> +}
>> +
>> +void
>> +set_log_cur(
>> +	const typ_t	*type,
>> +	xfs_daddr_t	blknum,
>> +	int		len,
>> +	int		ring_flag,
>> +	bbmap_t		*bbmap)
>> +{
>> +	struct xfs_buftarg	*btargp = mp->m_ddev_targp;
>> +
>> +	if (mp->m_logdev_targp->bt_bdev != mp->m_ddev_targp->bt_bdev) {
>> +		ASSERT(mp->m_sb.sb_logstart == 0);
>> +		btargp = mp->m_logdev_targp;
>> +	}
>
> I think this should print an error message if there isn't an external
> log device and then leave iocur_top unchanged:
>
> 	if (mp->m_logdev_targp->bt_bdev == mp->m_ddev_targp->bt_bdev) {
> 		fprintf(stderr, "no external log specified\n");
> 		exitcode = 1;
> 		return;
> 	}
>
> 	__set_cur(mp->m_logdev_targp, type, blknum, len, ring_flag, bbmap);
>
> because metadump shouldn't crash if there's an external log device but
> sb_logstart is zero.  The superblock fields /could/ be corrupt, or other
> weird shenanigans are going on.
>
> (Also it's a layering violation for the io cursors to know anything at
> all about the filesystem stored above them.)
>

I agree with your review comment. I will make the required changes.

-- 
chandan

  reply	other threads:[~2023-07-13  6:40 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2ExBvYxYPnyiGvOJzODNvNXx_bfn5RWAck_7UcV7OvxkF6fgAy6UZtI6d2-FdmxoIeBLPPX0vwW9uaJxBa5Rmg==@protonmail.internalid>
2023-06-06  9:27 ` [PATCH V2 00/23] Metadump v2 Chandan Babu R
2023-06-06  9:27   ` [PATCH V2 01/23] metadump: Use boolean values true/false instead of 1/0 Chandan Babu R
2023-06-06  9:27   ` [PATCH V2 02/23] mdrestore: Fix logic used to check if target device is large enough Chandan Babu R
2023-06-06  9:27   ` [PATCH V2 03/23] metadump: Declare boolean variables with bool type Chandan Babu R
2023-06-06 15:17     ` Darrick J. Wong
2023-06-06  9:27   ` [PATCH V2 04/23] metadump: Define and use struct metadump Chandan Babu R
2023-07-12 18:12     ` Darrick J. Wong
2023-07-20 13:13       ` Carlos Maiolino
2023-07-20 17:22         ` Darrick J. Wong
2023-06-06  9:27   ` [PATCH V2 05/23] metadump: Add initialization and release functions Chandan Babu R
2023-06-06  9:27   ` [PATCH V2 06/23] metadump: Postpone invocation of init_metadump() Chandan Babu R
2023-07-12 17:00     ` Darrick J. Wong
2023-06-06  9:27   ` [PATCH V2 07/23] metadump: Introduce struct metadump_ops Chandan Babu R
2023-07-12 17:06     ` Darrick J. Wong
2023-06-06  9:27   ` [PATCH V2 08/23] metadump: Introduce metadump v1 operations Chandan Babu R
2023-07-12 17:10     ` Darrick J. Wong
2023-07-13  4:36       ` Chandan Babu R
2023-06-06  9:27   ` [PATCH V2 09/23] metadump: Rename XFS_MD_MAGIC to XFS_MD_MAGIC_V1 Chandan Babu R
2023-06-06  9:27   ` [PATCH V2 10/23] metadump: Define metadump v2 ondisk format structures and macros Chandan Babu R
2023-07-12 17:18     ` Darrick J. Wong
2023-07-13  4:37       ` Chandan Babu R
2023-06-06  9:27   ` [PATCH V2 11/23] metadump: Define metadump ops for v2 format Chandan Babu R
2023-07-12 17:22     ` Darrick J. Wong
2023-07-13  4:45       ` Chandan Babu R
2023-06-06  9:27   ` [PATCH V2 12/23] xfs_db: Add support to read from external log device Chandan Babu R
2023-07-12 17:35     ` Darrick J. Wong
2023-07-13  5:24       ` Chandan Babu R [this message]
2023-06-06  9:27   ` [PATCH V2 13/23] metadump: Add support for passing version option Chandan Babu R
2023-06-06  9:27   ` [PATCH V2 14/23] mdrestore: Declare boolean variables with bool type Chandan Babu R
2023-07-12 17:35     ` Darrick J. Wong
2023-06-06  9:27   ` [PATCH V2 15/23] mdrestore: Define and use struct mdrestore Chandan Babu R
2023-07-12 18:12     ` Darrick J. Wong
2023-06-06  9:27   ` [PATCH V2 16/23] mdrestore: Detect metadump v1 magic before reading the header Chandan Babu R
2023-07-12 17:38     ` Darrick J. Wong
2023-06-06  9:28   ` [PATCH V2 17/23] mdrestore: Add open_device(), read_header() and show_info() functions Chandan Babu R
2023-07-12 17:46     ` Darrick J. Wong
2023-07-13  5:27       ` Chandan Babu R
2023-06-06  9:28   ` [PATCH V2 18/23] mdrestore: Introduce struct mdrestore_ops Chandan Babu R
2023-06-06  9:28   ` [PATCH V2 19/23] mdrestore: Replace metadump header pointer argument with generic pointer type Chandan Babu R
2023-07-12 17:55     ` Darrick J. Wong
2023-07-13  6:08       ` Chandan Babu R
2023-06-06  9:28   ` [PATCH V2 20/23] mdrestore: Introduce mdrestore v1 operations Chandan Babu R
2023-07-12 17:57     ` Darrick J. Wong
2023-06-06  9:28   ` [PATCH V2 21/23] mdrestore: Extract target device size verification into a function Chandan Babu R
2023-06-06  9:28   ` [PATCH V2 22/23] mdrestore: Define mdrestore ops for v2 format Chandan Babu R
2023-07-12 18:10     ` Darrick J. Wong
2023-07-13  6:27       ` Chandan Babu R
2023-07-13 14:22         ` Darrick J. Wong
2023-06-06  9:28   ` [PATCH V2 23/23] mdrestore: Add support for passing log device as an argument Chandan Babu R
2023-07-12 18:10     ` Darrick J. Wong
     [not found]       ` <181e7cbefa39e2dc59f2564c25966ac0d05aa6530483b7eb5d649de9a3d1cf7f@mu.id>
2023-07-13  6:48         ` Chandan Babu R
2023-06-06 12:10   ` [PATCH V2 00/23] Metadump v2 Carlos Maiolino
2023-06-06 12:38     ` Chandan Babu R
2023-06-06 16:04       ` Carlos Maiolino

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=87a5w0jouy.fsf@debian-BULLSEYE-live-builder-AMD64 \
    --to=chandan.babu@oracle.com \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --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 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.