This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/22321] New: sysconf(_SC_IOV_MAX) returns -1 on Linux


https://sourceware.org/bugzilla/show_bug.cgi?id=22321

            Bug ID: 22321
           Summary: sysconf(_SC_IOV_MAX) returns -1 on Linux
           Product: glibc
           Version: 2.26
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: fweimer at redhat dot com
                CC: drepper.fsp at gmail dot com, zackw at panix dot com
  Target Milestone: ---
             Flags: security-

But the kernel defines

#define UIO_MAXIOV     1024

in include/uapi/linux/uio.h, and uses that definition.

Reported first here:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/KURGEUYR4HLV43WHGZV236SYTJUW7YRU/

Introduced by:

commit 37f802f86400684c8d13403958b2c598721d6360
Author: Zack Weinberg <zackw@panix.com>
Date:   Wed Mar 22 10:55:38 2017 -0400

    Remove __need_IOV_MAX and __need_FOPEN_MAX.

It looks like the fix is to include <sys/uio.h> in sysdeps/posix/sysconf.c;
previously UIO_MAXIOV was supplied (indirectly) through <bits/stdio_lim.h>.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]