From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs_io: rework includes for statx structures
Date: Tue, 30 Apr 2019 13:15:33 -0700 [thread overview]
Message-ID: <20190430201533.GI5207@magnolia> (raw)
In-Reply-To: <cec15436-c098-c59f-2663-a6a189e46a0c@redhat.com>
On Tue, Apr 30, 2019 at 03:02:56PM -0500, Eric Sandeen wrote:
> Only include the kernel's linux/stat.h headers if we haven't
> already picked up statx bits from glibc, to avoid redefinition.
>
> Suggested-by: Darrick J. Wong <darrick.wong@oracle.com>
> Tested-by: Bill O'Donnell <billodo@redhat.com>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
We'll never have problems again!! :D
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
(I built it on Ubuntu 18.04 LTS if anyone cares)
--D
> ---
>
> diff --git a/io/stat.c b/io/stat.c
> index 517be66..37c0b2e 100644
> --- a/io/stat.c
> +++ b/io/stat.c
> @@ -6,9 +6,6 @@
> * Portions of statx support written by David Howells (dhowells@redhat.com)
> */
>
> -/* Try to pick up statx definitions from the system headers. */
> -#include <linux/stat.h>
> -
> #include "command.h"
> #include "input.h"
> #include "init.h"
> diff --git a/io/statx.h b/io/statx.h
> index 4f40eaa..c6625ac 100644
> --- a/io/statx.h
> +++ b/io/statx.h
> @@ -33,7 +33,14 @@
> # endif
> #endif
>
> +
> +#ifndef STATX_TYPE
> +/* Pick up kernel definitions if glibc didn't already provide them */
> +#include <linux/stat.h>
> +#endif
> +
> #ifndef STATX_TYPE
> +/* Local definitions if glibc & kernel headers didn't already provide them */
>
> /*
> * Timestamp structure for the timestamps in struct statx.
>
next prev parent reply other threads:[~2019-04-30 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 20:02 [PATCH] xfs_io: rework includes for statx structures Eric Sandeen
2019-04-30 20:15 ` Darrick J. Wong [this message]
2019-04-30 21:00 ` Bill O'Donnell
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=20190430201533.GI5207@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.