public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/14964] New: Constants for Linux fallocate() are not defined
@ 2012-12-16 15:38 mtk.manpages at gmail dot com
  2013-01-10  9:04 ` [Bug libc/14964] " schwab@linux-m68k.org
  2014-06-14  5:34 ` fweimer at redhat dot com
  0 siblings, 2 replies; 3+ messages in thread
From: mtk.manpages at gmail dot com @ 2012-12-16 15:38 UTC (permalink / raw)
  To: glibc-bugs

http://sourceware.org/bugzilla/show_bug.cgi?id=14964

             Bug #: 14964
           Summary: Constants for Linux fallocate() are not defined
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: unassigned@sourceware.org
        ReportedBy: mtk.manpages@gmail.com
                CC: drepper.fsp@gmail.com
    Classification: Unclassified


As a result of http://www.sourceware.org/bugzilla/show_bug.cgi?id=7083 , glibc
added support for the Linux fallocate() system call. However, the constants
needed for the 'mode' argument argument are missing from header files. That is,
bits/fcntl.h lacks the following definitions (from the Linux kernel source file
include/uapi/linux/falloc.h):

#define FALLOC_FL_KEEP_SIZE     0x01 /* default is extend size */
#define FALLOC_FL_PUNCH_HOLE    0x02 /* de-allocates range */

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-06-14  5:34 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-12-16 15:38 [Bug libc/14964] New: Constants for Linux fallocate() are not defined mtk.manpages at gmail dot com
2013-01-10  9:04 ` [Bug libc/14964] " schwab@linux-m68k.org
2014-06-14  5:34 ` fweimer at redhat dot com

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).