From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
Paul Eggert <eggert@cs.ucla.edu>,
libc-alpha@sourceware.org
Subject: Re: [PATCH] Add the statx function
Date: Thu, 05 Jul 2018 19:06:00 -0000 [thread overview]
Message-ID: <4d3e7e55-fc34-bc3b-6d9e-afef45fc4d9e@redhat.com> (raw)
In-Reply-To: <b1fd37e8-4fc5-9335-ab30-3685ab78be1f@redhat.com>
On 07/05/2018 02:59 PM, Florian Weimer wrote:
> On 07/05/2018 08:36 PM, Paul Eggert wrote:
>> Florian Weimer wrote:
>>
>>> +Â *buf = (struct statx)
>>> +Â Â Â {
>>> +Â Â Â Â Â /* We copy everything from fstat64, which corresponds the basic
>>> +        fstat64. */
>>> +Â Â Â Â Â .stx_mask = STATX_BASIC_STATS,
>>
>> That assignment to *BUF unnecessarily clears all *BUF fields not mentioned. It should be a bit more efficient to have a separate assignment for each mentioned field, e.g., 'buf->stx_mask = STATX_BASIC_STATS;'.
>
> Clearing all padding fields is part of the userspace interface. It's described in the UAPI header file, and the kernel implements that.
>
> I've updated the comment.
>
> I also fixed a C&P mistake in the major/minor extraction.
>
>>> +int statx (int __dirfd, const char *__path, int __flags,
>>> +Â Â Â Â Â Â Â Â Â Â unsigned int __mask, struct statx *__buf)
>>> +Â __THROW __nonnull ((2, 5));
>>
>> The two pointer parameters should both be declared with __restrict.
>
> Okay, I've added __restrict qualifiers.
>
> As Andreas suggested, I've added STATX_ALL and STATX__RESERVED.
I'm not reviewing this yet.
However, as glibc 2.28 release manager I OK the addition of statx
into the release if you can get it reviewed in the next couple of
business days.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2018-07-05 19:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 22:41 Florian Weimer
2018-07-02 9:01 ` Andreas Schwab
2018-07-05 18:36 ` Paul Eggert
2018-07-05 18:59 ` Florian Weimer
2018-07-05 19:06 ` Carlos O'Donell [this message]
2018-07-07 23:23 ` Paul Eggert
2018-07-10 9:16 ` Florian Weimer
2018-07-10 12:14 ` Carlos O'Donell
2018-07-10 14:19 ` Florian Weimer
2018-07-11 6:53 ` Andreas Schwab
2018-07-11 6:55 ` Florian Weimer
2018-07-11 10:01 ` Szabolcs Nagy
2018-07-11 13:44 ` Jeff Law
2018-07-26 15:16 ` Florian Weimer
2018-07-26 19:38 ` Andreas Schwab
2018-07-26 21:16 ` Florian Weimer
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=4d3e7e55-fc34-bc3b-6d9e-afef45fc4d9e@redhat.com \
--to=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).