From: Jeff Mahoney <jeffm@suse.com>
To: Eric Sandeen <sandeen@sandeen.net>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs_io: stat: treat statfs.f_flags as optional
Date: Mon, 20 Nov 2017 13:13:38 -0500 [thread overview]
Message-ID: <671af24c-77d7-7826-5067-8349a5835170@suse.com> (raw)
In-Reply-To: <b6e0865f-5528-c7c9-9663-1a14e660c243@sandeen.net>
[-- Attachment #1.1: Type: text/plain, Size: 1046 bytes --]
On 11/20/17 1:10 PM, Eric Sandeen wrote:
>
>
> On 11/20/17 11:54 AM, Eric Sandeen wrote:
>>
>>
>> On 11/17/17 1:54 PM, jeffm@suse.com wrote:
>>> From: Jeff Mahoney <jeffm@suse.com>
>>>
>>> Kernels prior to 2.6.36 didn't contain statfs.f_flags. Distros with
>>> initial releases with kernels prior to this may not have updated
>>> headers with this member.
>>
>> You all are brave ;)
>>
>> Reviewed-by: Eric Sandeen <sandeen@redhat.com>
>
> Oops, but not tested-by! This also needs:
>
> diff --git a/io/Makefile b/io/Makefile
> index 050d6bd..6725936 100644
> --- a/io/Makefile
> +++ b/io/Makefile
> @@ -110,6 +110,10 @@ ifeq ($(PKG_PLATFORM),linux)
> CFILES += fsmap.c
> endif
>
> +ifeq ($(HAVE_STATFS_FLAGS),yes)
> +LCFLAGS += -DHAVE_STATFS_FLAGS
> +endif
> +
> default: depend $(LTCOMMAND)
>
> include $(BUILDRULES)
>
>
> but I can add it on the way in.
Ah, right. My build tests all succeeded because it was just skipping
f_flags.
Thanks,
-Jeff
--
Jeff Mahoney
SUSE Labs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
next prev parent reply other threads:[~2017-11-20 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 19:54 [PATCH 1/2] xfs_io: stat: fix typo in statfs->f_flags jeffm
2017-11-17 19:54 ` [PATCH 2/2] xfs_io: stat: treat statfs.f_flags as optional jeffm
2017-11-20 17:54 ` Eric Sandeen
2017-11-20 18:10 ` Eric Sandeen
2017-11-20 18:13 ` Jeff Mahoney [this message]
2017-11-20 17:48 ` [PATCH 1/2] xfs_io: stat: fix typo in statfs->f_flags Eric Sandeen
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=671af24c-77d7-7826-5067-8349a5835170@suse.com \
--to=jeffm@suse.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;
as well as URLs for NNTP newsgroup(s).