public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: libc-alpha@sourceware.org
Cc: Peter TB Brett <peter@peter-b.co.uk>
Subject: Re: [PATCH][BZ 15514] Use statvfs64() for pathconf(_PC_NAME_MAX).
Date: Tue, 08 Apr 2014 23:10:00 -0000	[thread overview]
Message-ID: <5487193.CL6ltikRKQ@vapier> (raw)
In-Reply-To: <87ioqk270z.fsf@harrington.peter-b.co.uk>

[-- Attachment #1: Type: text/plain, Size: 365 bytes --]

On Mon 07 Apr 2014 21:56:12 Peter TB Brett wrote:
> pathconf(_PC_NAME_MAX) was implemented on top of statfs().  The 32bit
> version therefore fails EOVERFLOW if the filesystem blockcount is
> sufficiently large.
> 
> Most pathconf() queries use statvfs64(), which avoids this issue.  This
> patch modifies pathconf(_PC_NAME_MAX) to do likewise.

lgtm
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2014-04-08 23:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 20:56 Peter TB Brett
2014-04-08 15:10 ` Ondřej Bílka
2014-04-08 23:10 ` Mike Frysinger [this message]

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=5487193.CL6ltikRKQ@vapier \
    --to=vapier@gentoo.org \
    --cc=libc-alpha@sourceware.org \
    --cc=peter@peter-b.co.uk \
    /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).