From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Chen Li <chenli@uniontech.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] statfs: add missing f_flags assignment
Date: Wed, 14 Oct 2020 10:01:05 +0200 [thread overview]
Message-ID: <87k0vtqlry.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <87r1q4t2sn.wl-chenli@uniontech.com> (Chen Li's message of "Mon, 12 Oct 2020 13:46:00 +0800")
* Chen Li:
> f_flags is added into struct statfs since Linux 2.6.36, which is lacked
> in glibc's statfs64.c until now. So mount flags is uninitialized on
> platforms having no statfs64 syscall in kernel, e.g., alpha and its derivation
>
> Signed-off-by: chenli <chenli@uniontech.com>
> ---
> sysdeps/unix/sysv/linux/statfs64.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/sysdeps/unix/sysv/linux/statfs64.c b/sysdeps/unix/sysv/linux/statfs64.c
> index c941128637..2c293badc8 100644
> --- a/sysdeps/unix/sysv/linux/statfs64.c
> +++ b/sysdeps/unix/sysv/linux/statfs64.c
> @@ -78,6 +78,7 @@ __statfs64 (const char *file, struct statfs64 *buf)
> buf->f_fsid = buf32.f_fsid;
> buf->f_namelen = buf32.f_namelen;
> buf->f_frsize = buf32.f_frsize;
> + buf->f_flags = buf32.f_flags;
> memcpy (buf->f_spare, buf32.f_spare, sizeof (buf32.f_spare));
>
> return 0;
I've checked that this builds on all architectures.
Does this result in a user-visible bug on some architectures besides
alpha?
May we drop the “Signed-off-by: chenli <chenli@uniontech.com>” line?
glibc does not use DCO <https://developercertificate.org/>, but due to
the size of the change, no additional paperwork is required for this
contribution.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2020-10-14 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 5:46 [PATCH] statfs: add missing f_flags assignment Chen Li
2020-10-14 8:01 ` Florian Weimer via Libc-alpha [this message]
2020-10-15 9:00 ` Chen Li
2020-10-15 9:42 ` Florian Weimer via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0vtqlry.fsf@oldenburg2.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=chenli@uniontech.com \
--cc=fweimer@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 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).