public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "peter@peter-b.co.uk" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/15514] pathconf(_PC_NAME_MAX) fails against large filesystems for 32bit processes Date: Sun, 06 Apr 2014 09:56:00 -0000 [thread overview] Message-ID: <bug-15514-131-bclQp5LQT2@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15514-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15514 Peter TB Brett <peter@peter-b.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peter@peter-b.co.uk --- Comment #2 from Peter TB Brett <peter@peter-b.co.uk> --- Created attachment 7538 --> https://sourceware.org/bugzilla/attachment.cgi?id=7538&action=edit Proposed patch Something like the attached? Most of the pathconf queries use statvfs64(), so it didn't seem unreasonable to make _PC_NAME_MAX do the same. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-04-06 9:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-22 5:29 [Bug libc/15514] New: " guenther at gmail dot com 2013-05-22 7:29 ` [Bug libc/15514] " schwab@linux-m68k.org 2014-04-06 9:56 ` peter@peter-b.co.uk [this message] 2014-06-13 13:49 ` fweimer at redhat dot com
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=bug-15514-131-bclQp5LQT2@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).