From: Brian Foster <bfoster@redhat.com>
To: Gao Xiang <hsiangkao@redhat.com>
Cc: linux-xfs@vger.kernel.org,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Eric Sandeen <sandeen@sandeen.net>,
Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@redhat.com>
Subject: Re: [PATCH v6 2/7] xfs: get rid of xfs_growfs_{data,log}_t
Date: Tue, 2 Feb 2021 14:37:48 -0500 [thread overview]
Message-ID: <20210202193748.GM3336100@bfoster> (raw)
In-Reply-To: <20210126125621.3846735-3-hsiangkao@redhat.com>
On Tue, Jan 26, 2021 at 08:56:16PM +0800, Gao Xiang wrote:
> Such usage isn't encouraged by the kernel coding style. Leave the
> definitions alone in case of userspace users.
>
> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
> Reviewed-by: Eric Sandeen <sandeen@redhat.com>
> Signed-off-by: Gao Xiang <hsiangkao@redhat.com>
> ---
Reviewed-by: Brian Foster <bfoster@redhat.com>
> fs/xfs/xfs_fsops.c | 12 ++++++------
> fs/xfs/xfs_fsops.h | 4 ++--
> fs/xfs/xfs_ioctl.c | 4 ++--
> 3 files changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/fs/xfs/xfs_fsops.c b/fs/xfs/xfs_fsops.c
> index 62600d78bbf1..a2a407039227 100644
> --- a/fs/xfs/xfs_fsops.c
> +++ b/fs/xfs/xfs_fsops.c
> @@ -25,8 +25,8 @@
> */
> static int
> xfs_growfs_data_private(
> - xfs_mount_t *mp, /* mount point for filesystem */
> - xfs_growfs_data_t *in) /* growfs data input struct */
> + struct xfs_mount *mp, /* mount point for filesystem */
> + struct xfs_growfs_data *in) /* growfs data input struct */
> {
> struct xfs_buf *bp;
> int error;
> @@ -35,7 +35,7 @@ xfs_growfs_data_private(
> xfs_rfsblock_t nb, nb_div, nb_mod;
> xfs_rfsblock_t delta;
> xfs_agnumber_t oagcount;
> - xfs_trans_t *tp;
> + struct xfs_trans *tp;
> struct aghdr_init_data id = {};
>
> nb = in->newblocks;
> @@ -170,8 +170,8 @@ xfs_growfs_data_private(
>
> static int
> xfs_growfs_log_private(
> - xfs_mount_t *mp, /* mount point for filesystem */
> - xfs_growfs_log_t *in) /* growfs log input struct */
> + struct xfs_mount *mp, /* mount point for filesystem */
> + struct xfs_growfs_log *in) /* growfs log input struct */
> {
> xfs_extlen_t nb;
>
> @@ -268,7 +268,7 @@ xfs_growfs_data(
> int
> xfs_growfs_log(
> xfs_mount_t *mp,
> - xfs_growfs_log_t *in)
> + struct xfs_growfs_log *in)
> {
> int error;
>
> diff --git a/fs/xfs/xfs_fsops.h b/fs/xfs/xfs_fsops.h
> index 92869f6ec8d3..2cffe51a31e8 100644
> --- a/fs/xfs/xfs_fsops.h
> +++ b/fs/xfs/xfs_fsops.h
> @@ -6,8 +6,8 @@
> #ifndef __XFS_FSOPS_H__
> #define __XFS_FSOPS_H__
>
> -extern int xfs_growfs_data(xfs_mount_t *mp, xfs_growfs_data_t *in);
> -extern int xfs_growfs_log(xfs_mount_t *mp, xfs_growfs_log_t *in);
> +extern int xfs_growfs_data(struct xfs_mount *mp, struct xfs_growfs_data *in);
> +extern int xfs_growfs_log(struct xfs_mount *mp, struct xfs_growfs_log *in);
> extern void xfs_fs_counts(xfs_mount_t *mp, xfs_fsop_counts_t *cnt);
> extern int xfs_reserve_blocks(xfs_mount_t *mp, uint64_t *inval,
> xfs_fsop_resblks_t *outval);
> diff --git a/fs/xfs/xfs_ioctl.c b/fs/xfs/xfs_ioctl.c
> index 3fbd98f61ea5..a62520f49ec5 100644
> --- a/fs/xfs/xfs_ioctl.c
> +++ b/fs/xfs/xfs_ioctl.c
> @@ -2260,7 +2260,7 @@ xfs_file_ioctl(
> }
>
> case XFS_IOC_FSGROWFSDATA: {
> - xfs_growfs_data_t in;
> + struct xfs_growfs_data in;
>
> if (copy_from_user(&in, arg, sizeof(in)))
> return -EFAULT;
> @@ -2274,7 +2274,7 @@ xfs_file_ioctl(
> }
>
> case XFS_IOC_FSGROWFSLOG: {
> - xfs_growfs_log_t in;
> + struct xfs_growfs_log in;
>
> if (copy_from_user(&in, arg, sizeof(in)))
> return -EFAULT;
> --
> 2.27.0
>
next prev parent reply other threads:[~2021-02-02 19:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 12:56 [PATCH v6 0/7] xfs: support shrinking free space in the last AG Gao Xiang
2021-01-26 12:56 ` [PATCH v6 1/7] xfs: rename `new' to `delta' in xfs_growfs_data_private() Gao Xiang
2021-02-02 19:37 ` Brian Foster
2021-01-26 12:56 ` [PATCH v6 2/7] xfs: get rid of xfs_growfs_{data,log}_t Gao Xiang
2021-02-02 19:37 ` Brian Foster [this message]
2021-01-26 12:56 ` [PATCH v6 3/7] xfs: update lazy sb counters immediately for resizefs Gao Xiang
2021-02-02 19:38 ` Brian Foster
2021-02-03 0:45 ` Gao Xiang
2021-01-26 12:56 ` [PATCH v6 4/7] xfs: hoist out xfs_resizefs_init_new_ags() Gao Xiang
2021-02-02 19:38 ` Brian Foster
2021-01-26 12:56 ` [PATCH v6 5/7] xfs: introduce xfs_ag_shrink_space() Gao Xiang
2021-01-26 12:56 ` [PATCH v6 6/7] xfs: support shrinking unused space in the last AG Gao Xiang
2021-02-03 14:23 ` Brian Foster
2021-02-03 14:51 ` Gao Xiang
2021-02-03 18:01 ` Brian Foster
2021-02-04 9:18 ` Gao Xiang
2021-02-04 12:33 ` Brian Foster
2021-02-04 16:21 ` Gao Xiang
2021-02-03 18:12 ` Darrick J. Wong
2021-02-03 18:14 ` Darrick J. Wong
2021-02-03 19:02 ` Gao Xiang
2021-02-03 19:19 ` Gao Xiang
2021-02-04 12:33 ` Brian Foster
2021-02-04 13:58 ` Gao Xiang
2021-02-04 9:40 ` Gao Xiang
2021-01-26 12:56 ` [PATCH v6 7/7] xfs: add error injection for per-AG resv failure when shrinkfs Gao Xiang
2021-02-03 14:23 ` Brian Foster
2021-02-03 15:01 ` Gao Xiang
2021-02-03 18:01 ` Brian Foster
2021-02-04 9:20 ` Gao Xiang
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=20210202193748.GM3336100@bfoster \
--to=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=hsiangkao@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
/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