Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: cem@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: remove the EXPERIMENTAL warning for pNFS
Date: Tue, 13 May 2025 07:36:32 -0700	[thread overview]
Message-ID: <20250513143632.GJ2701446@frogsfrogsfrogs> (raw)
In-Reply-To: <20250513053102.757788-1-hch@lst.de>

On Tue, May 13, 2025 at 07:30:33AM +0200, Christoph Hellwig wrote:
> The pNFS layout support has been around for 10 years without major
> issues, drop the EXPERIMENTAL warning.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> 
> This is ontop of "xfs: remove some EXPERIMENTAL warnings" from Darrick.
> 
>  fs/xfs/xfs_message.c | 4 ----
>  fs/xfs/xfs_message.h | 1 -
>  fs/xfs/xfs_pnfs.c    | 2 --
>  3 files changed, 7 deletions(-)
> 
> diff --git a/fs/xfs/xfs_message.c b/fs/xfs/xfs_message.c
> index 54fc5ada519c..19aba2c3d525 100644
> --- a/fs/xfs/xfs_message.c
> +++ b/fs/xfs/xfs_message.c
> @@ -141,10 +141,6 @@ xfs_warn_experimental(
>  		const char		*name;
>  		long			opstate;
>  	} features[] = {
> -		[XFS_EXPERIMENTAL_PNFS] = {
> -			.opstate	= XFS_OPSTATE_WARNED_PNFS,

Looks fine, but you ought to remove XFS_OPSTATE_WARNED_PNFS from
xfs_mount.h as I forgot to do in my patch. :(

--D

> -			.name		= "pNFS",
> -		},
>  		[XFS_EXPERIMENTAL_SHRINK] = {
>  			.opstate	= XFS_OPSTATE_WARNED_SHRINK,
>  			.name		= "online shrink",
> diff --git a/fs/xfs/xfs_message.h b/fs/xfs/xfs_message.h
> index bce9942f394a..d68e72379f9d 100644
> --- a/fs/xfs/xfs_message.h
> +++ b/fs/xfs/xfs_message.h
> @@ -91,7 +91,6 @@ void xfs_buf_alert_ratelimited(struct xfs_buf *bp, const char *rlmsg,
>  			       const char *fmt, ...);
>  
>  enum xfs_experimental_feat {
> -	XFS_EXPERIMENTAL_PNFS,
>  	XFS_EXPERIMENTAL_SHRINK,
>  	XFS_EXPERIMENTAL_LARP,
>  	XFS_EXPERIMENTAL_LBS,
> diff --git a/fs/xfs/xfs_pnfs.c b/fs/xfs/xfs_pnfs.c
> index 6f4479deac6d..afe7497012d4 100644
> --- a/fs/xfs/xfs_pnfs.c
> +++ b/fs/xfs/xfs_pnfs.c
> @@ -58,8 +58,6 @@ xfs_fs_get_uuid(
>  {
>  	struct xfs_mount	*mp = XFS_M(sb);
>  
> -	xfs_warn_experimental(mp, XFS_EXPERIMENTAL_PNFS);
> -
>  	if (*len < sizeof(uuid_t))
>  		return -EINVAL;
>  
> -- 
> 2.47.2
> 
> 

      parent reply	other threads:[~2025-05-13 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ameUfBEEyURNYSQYgyjG-wGKYZUzJ1k2wPEZcnDB5ONjpQoDTTLROlafcZbTzuQyBGclnKN-bPmGKpwL4SwGrg==@protonmail.internalid>
2025-05-13  5:30 ` [PATCH] xfs: remove the EXPERIMENTAL warning for pNFS Christoph Hellwig
2025-05-13  8:50   ` Carlos Maiolino
2025-05-13 14:36   ` Darrick J. Wong [this message]

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=20250513143632.GJ2701446@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@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