From: Dave Chinner <david@fromorbit.com>
To: Gao Xiang <hsiangkao@redhat.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-xfs@vger.kernel.org, Brian Foster <bfoster@redhat.com>
Subject: Re: [PATCH v3 2/4] xfs: get rid of xfs_growfs_{data,log}_t
Date: Mon, 11 Jan 2021 08:04:36 +1100 [thread overview]
Message-ID: <20210110210436.GM331610@dread.disaster.area> (raw)
In-Reply-To: <20210109004934.GB660098@xiangao.remote.csb>
On Sat, Jan 09, 2021 at 08:49:34AM +0800, Gao Xiang wrote:
> On Fri, Jan 08, 2021 at 03:27:21PM -0600, Eric Sandeen wrote:
> > On 1/8/21 3:21 PM, Darrick J. Wong wrote:
> > > On Sat, Jan 09, 2021 at 03:09:17AM +0800, Gao Xiang wrote:
> > >> Such usage isn't encouraged by the kernel coding style.
> > >>
> > >> Signed-off-by: Gao Xiang <hsiangkao@redhat.com>
> > >> ---
> > >> fs/xfs/libxfs/xfs_fs.h | 4 ++--
> > >> fs/xfs/xfs_fsops.c | 12 ++++++------
> > >> fs/xfs/xfs_fsops.h | 4 ++--
> > >> fs/xfs/xfs_ioctl.c | 4 ++--
> > >> 4 files changed, 12 insertions(+), 12 deletions(-)
> > >>
> > >> diff --git a/fs/xfs/libxfs/xfs_fs.h b/fs/xfs/libxfs/xfs_fs.h
> > >> index 2a2e3cfd94f0..a17313efc1fe 100644
> > >> --- a/fs/xfs/libxfs/xfs_fs.h
> > >> +++ b/fs/xfs/libxfs/xfs_fs.h
> > >> @@ -308,12 +308,12 @@ struct xfs_ag_geometry {
> > >> typedef struct xfs_growfs_data {
> > >> __u64 newblocks; /* new data subvol size, fsblocks */
> > >> __u32 imaxpct; /* new inode space percentage limit */
> > >> -} xfs_growfs_data_t;
> > >> +};
> > >
> > > So long as Eric is ok with fixing this up in xfs_fs_compat.h in
> > > userspace,
> > >
> > > Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > Sure, why not :) (tho is growfs really a public interface? I guess so,
> > technically, though not documented as such.)
They are not described in man pages, though they are listed in
xfsctl(3) so they are definitely public interfaces.
> Yeah, although I think nobody else uses it (I could leave the typedef
> definitions only if needed otherwise...)
It is used elsewhere - ISTR that it is used by a couple of third
party applications that integrate growing filesystems into their
other storage management tasks.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2021-01-10 21:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 19:09 [PATCH v3 0/4] xfs: support shrinking free space in the last AG Gao Xiang
2021-01-08 19:09 ` [PATCH v3 1/4] xfs: rename `new' to `delta' in xfs_growfs_data_private() Gao Xiang
2021-01-08 21:23 ` Darrick J. Wong
2021-01-08 19:09 ` [PATCH v3 2/4] xfs: get rid of xfs_growfs_{data,log}_t Gao Xiang
2021-01-08 21:21 ` Darrick J. Wong
2021-01-08 21:27 ` Eric Sandeen
2021-01-09 0:49 ` Gao Xiang
2021-01-10 21:04 ` Dave Chinner [this message]
2021-01-11 0:17 ` Gao Xiang
2021-01-11 17:30 ` Christoph Hellwig
2021-01-11 18:02 ` Gao Xiang
2021-01-08 19:09 ` [PATCH v3 3/4] xfs: hoist out xfs_resizefs_init_new_ags() Gao Xiang
2021-01-08 21:20 ` Darrick J. Wong
2021-01-11 17:32 ` Christoph Hellwig
2021-01-11 17:47 ` Gao Xiang
2021-01-08 19:09 ` [PATCH v3 4/4] xfs: support shrinking unused space in the last AG Gao Xiang
2021-01-08 21:19 ` Darrick J. Wong
2021-01-09 0:47 ` 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=20210110210436.GM331610@dread.disaster.area \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=hsiangkao@redhat.com \
--cc=linux-xfs@vger.kernel.org \
--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