public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Iliopoulos <ailiop@suse.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs: deprecate BMV_IF_NO_DMAPI_READ flag
Date: Wed, 31 Mar 2021 19:06:05 +0200	[thread overview]
Message-ID: <YGSr/Yyv5EaYSb35@technoir> (raw)
In-Reply-To: <20210331163114.GC4090233@magnolia>

On Wed, Mar 31, 2021 at 09:31:14AM -0700, Darrick J. Wong wrote:
> On Wed, Mar 31, 2021 at 06:26:16PM +0200, Anthony Iliopoulos wrote:
> > Use of the flag has had no effect since kernel commit 288699fecaff
> > ("xfs: drop dmapi hooks"), which removed all dmapi related code, so
> > deprecate it.
> > 
> > Signed-off-by: Anthony Iliopoulos <ailiop@suse.com>
> > ---
> > changes since v1:
> >  - retain flag definition to prevent reuse and not break kabi, per
> >    Darrick's suggestion.
> > 
> >  fs/xfs/libxfs/xfs_fs.h | 4 ++--
> >  fs/xfs/xfs_ioctl.c     | 2 --
> >  2 files changed, 2 insertions(+), 4 deletions(-)
> > 
> > diff --git a/fs/xfs/libxfs/xfs_fs.h b/fs/xfs/libxfs/xfs_fs.h
> > index 6fad140d4c8e..4ef813e00e9e 100644
> > --- a/fs/xfs/libxfs/xfs_fs.h
> > +++ b/fs/xfs/libxfs/xfs_fs.h
> > @@ -65,13 +65,13 @@ struct getbmapx {
> >  
> >  /*	bmv_iflags values - set by XFS_IOC_GETBMAPX caller.	*/
> >  #define BMV_IF_ATTRFORK		0x1	/* return attr fork rather than data */
> > -#define BMV_IF_NO_DMAPI_READ	0x2	/* Do not generate DMAPI read event  */
> > +#define BMV_IF_NO_DMAPI_READ	0x2	/* Deprecated */
> >  #define BMV_IF_PREALLOC		0x4	/* rtn status BMV_OF_PREALLOC if req */
> >  #define BMV_IF_DELALLOC		0x8	/* rtn status BMV_OF_DELALLOC if req */
> >  #define BMV_IF_NO_HOLES		0x10	/* Do not return holes */
> >  #define BMV_IF_COWFORK		0x20	/* return CoW fork rather than data */
> >  #define BMV_IF_VALID	\
> > -	(BMV_IF_ATTRFORK|BMV_IF_NO_DMAPI_READ|BMV_IF_PREALLOC|	\
> > +	(BMV_IF_ATTRFORK|BMV_IF_PREALLOC|	\
> >  	 BMV_IF_DELALLOC|BMV_IF_NO_HOLES|BMV_IF_COWFORK)
> 
> What about the xfs/296 regression that the kernel robot reported?
> 
> I /think/ that's a result of removing this flag from BMV_IF_VALID, which
> is used to reject unknown input flags from the GETBMAP caller.  In the
> current upstream the flag is valid even if it does nothing, so we have
> to preserve that behavior.

In that case then it indeed needs to stay in BMV_IF_VALID. I assume it
is not worth putting flags into a deprecation schedule, so this will
have to stay there for as long as the ioctl exists. I'll send a v3.

Regards,
Anthony

      reply	other threads:[~2021-03-31 17:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 16:26 [PATCH v2] xfs: deprecate BMV_IF_NO_DMAPI_READ flag Anthony Iliopoulos
2021-03-31 16:31 ` Darrick J. Wong
2021-03-31 17:06   ` Anthony Iliopoulos [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=YGSr/Yyv5EaYSb35@technoir \
    --to=ailiop@suse.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox