From: "Darrick J. Wong" <djwong@kernel.org>
To: Anthony Iliopoulos <ailiop@suse.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: remove BMV_IF_NO_DMAPI_READ flag
Date: Fri, 26 Mar 2021 08:31:15 -0700 [thread overview]
Message-ID: <20210326153115.GT4090233@magnolia> (raw)
In-Reply-To: <20210326125321.28047-1-ailiop@suse.com>
On Fri, Mar 26, 2021 at 01:53:19PM +0100, 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
> drop it completely.
>
> Signed-off-by: Anthony Iliopoulos <ailiop@suse.com>
> ---
> fs/xfs/libxfs/xfs_fs.h | 3 +--
> fs/xfs/xfs_ioctl.c | 2 --
> 2 files changed, 1 insertion(+), 4 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_fs.h b/fs/xfs/libxfs/xfs_fs.h
> index 6fad140d4c8e..23da047c3098 100644
> --- a/fs/xfs/libxfs/xfs_fs.h
> +++ b/fs/xfs/libxfs/xfs_fs.h
> @@ -65,13 +65,12 @@ 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 */
I don't think we can drop this definition completely. Something has to
be here to discourage anyone from reusing 0x2, since there are
undoubtedly programs out there that will check for this. It's also not
a good idea to break kabi by removing names.
#define BMV_IF_NO_DMAPI_READ 0x2 /* Deprecated */
(Everything else in the patch looks fine.)
--D
> #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)
>
> /* bmv_oflags values - returned for each non-header segment */
> diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c
> index 99dfe89a8d08..9d3f72ef1efe 100644
> --- a/fs/xfs/xfs_ioctl.c
> +++ b/fs/xfs/xfs_ioctl.c
> @@ -1669,8 +1669,6 @@ xfs_ioc_getbmap(
> bmx.bmv_iflags = BMV_IF_ATTRFORK;
> /*FALLTHRU*/
> case XFS_IOC_GETBMAP:
> - if (file->f_mode & FMODE_NOCMTIME)
> - bmx.bmv_iflags |= BMV_IF_NO_DMAPI_READ;
> /* struct getbmap is a strict subset of struct getbmapx. */
> recsize = sizeof(struct getbmap);
> break;
> --
> 2.31.0
>
next prev parent reply other threads:[~2021-03-26 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 12:53 [PATCH] xfs: remove BMV_IF_NO_DMAPI_READ flag Anthony Iliopoulos
2021-03-26 15:31 ` Darrick J. Wong [this message]
2021-03-31 6:22 ` [xfs] 141cfc276a: xfstests.xfs.296.fail kernel test robot
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=20210326153115.GT4090233@magnolia \
--to=djwong@kernel.org \
--cc=ailiop@suse.com \
--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