public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Yuto Ohnuki <ytohnuki@amazon.com>
Cc: Carlos Maiolino <cem@kernel.org>, Dave Chinner <dgc@kernel.org>,
	linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] xfs: zero entire directory data block header region at init
Date: Mon, 13 Apr 2026 10:56:14 -0700	[thread overview]
Message-ID: <20260413175614.GL1048989@frogsfrogsfrogs> (raw)
In-Reply-To: <20260411142411.72194-6-ytohnuki@amazon.com>

On Sat, Apr 11, 2026 at 03:24:13PM +0100, Yuto Ohnuki wrote:
> xfs_dir3_data_init currently zeroes only the xfs_dir3_blk_hdr portion of
> the directory data block header, then manually initializes the bestfree
> entries in a loop. This leaves the pad field in xfs_dir3_data_hdr
> uninitialized and requires explicit zeroing of each bestfree slot.
> 
> Zero the entire header region (geo->data_entry_offset bytes)
> unconditionally before setting individual fields. This covers all
> current and future header fields, all padding (implicit and explicit),
> and the bestfree array, so the manual zeroing loop for bestfree can be
> removed.
> 
> Suggested-by: Dave Chinner <dgc@kernel.org>
> Signed-off-by: Yuto Ohnuki <ytohnuki@amazon.com>

Seems reasonable to me to zero the entire head including the bestfree
areas.

Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D

> ---
>  fs/xfs/libxfs/xfs_dir2_data.c | 12 +++++-------
>  1 file changed, 5 insertions(+), 7 deletions(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_dir2_data.c b/fs/xfs/libxfs/xfs_dir2_data.c
> index 80ba94f51e5c..35ff119aa84b 100644
> --- a/fs/xfs/libxfs/xfs_dir2_data.c
> +++ b/fs/xfs/libxfs/xfs_dir2_data.c
> @@ -728,7 +728,6 @@ xfs_dir3_data_init(
>  	struct xfs_dir2_data_unused	*dup;
>  	struct xfs_dir2_data_free 	*bf;
>  	int				error;
> -	int				i;
>  
>  	/*
>  	 * Get the buffer set up for the block.
> @@ -741,13 +740,16 @@ xfs_dir3_data_init(
>  	xfs_trans_buf_set_type(tp, bp, XFS_BLFT_DIR_DATA_BUF);
>  
>  	/*
> -	 * Initialize the header.
> +	 * Initialize the whole directory header region to zero
> +	 * so that all padding, bestfree entries, and any
> +	 * future header fields are clean.
>  	 */
>  	hdr = bp->b_addr;
> +	memset(hdr, 0, geo->data_entry_offset);
> +
>  	if (xfs_has_crc(mp)) {
>  		struct xfs_dir3_blk_hdr *hdr3 = bp->b_addr;
>  
> -		memset(hdr3, 0, sizeof(*hdr3));
>  		hdr3->magic = cpu_to_be32(XFS_DIR3_DATA_MAGIC);
>  		hdr3->blkno = cpu_to_be64(xfs_buf_daddr(bp));
>  		hdr3->owner = cpu_to_be64(args->owner);
> @@ -759,10 +761,6 @@ xfs_dir3_data_init(
>  	bf = xfs_dir2_data_bestfree_p(mp, hdr);
>  	bf[0].offset = cpu_to_be16(geo->data_entry_offset);
>  	bf[0].length = cpu_to_be16(geo->blksize - geo->data_entry_offset);
> -	for (i = 1; i < XFS_DIR2_DATA_FD_COUNT; i++) {
> -		bf[i].length = 0;
> -		bf[i].offset = 0;
> -	}
>  
>  	/*
>  	 * Set up an unused entry for the block's body.
> -- 
> 2.50.1
> 
> 
> 
> 
> Amazon Web Services EMEA SARL, 38 avenue John F. Kennedy, L-1855 Luxembourg, R.C.S. Luxembourg B186284
> 
> Amazon Web Services EMEA SARL, Irish Branch, One Burlington Plaza, Burlington Road, Dublin 4, Ireland, branch registration number 908705
> 
> 
> 
> 

  reply	other threads:[~2026-04-13 17:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-11 14:24 [PATCH v3 0/3] xfs: clean up directory data block header padding Yuto Ohnuki
2026-04-11 14:24 ` [PATCH v3 1/3] xfs: zero entire directory data block header region at init Yuto Ohnuki
2026-04-13 17:56   ` Darrick J. Wong [this message]
2026-04-11 14:24 ` [PATCH v3 2/3] xfs: zero directory data block padding on write verification Yuto Ohnuki
2026-04-13 17:59   ` Darrick J. Wong
2026-04-14  0:39     ` Dave Chinner
2026-04-14  1:01       ` Darrick J. Wong
2026-04-11 14:24 ` [PATCH v3 3/3] xfs: check directory data block header padding in scrub Yuto Ohnuki
2026-04-13 18:00   ` Darrick J. Wong

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=20260413175614.GL1048989@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=dgc@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ytohnuki@amazon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox