public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stefan.smorra at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/31430] New: glibc doesn't define MAP_UNINITIALIZED Date: Wed, 28 Feb 2024 17:59:11 +0000 [thread overview] Message-ID: <bug-31430-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31430 Bug ID: 31430 Summary: glibc doesn't define MAP_UNINITIALIZED Product: glibc Version: 2.39 Status: UNCONFIRMED Severity: minor Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: stefan.smorra at gmail dot com CC: drepper.fsp at gmail dot com Target Milestone: --- When you look into Linux 'man mmap' you'll find MAP_UNINITIALIZED which exists for roughly 14 years (in the Linux kernel). However when I include sys/mman.h it says MAP_UNINITIALIZED is undeclared. I am not 100% sure if this is a bug in glibc or intention. I searched the web, mailing lists, stackoverflow and the glibc source code and found nothing about why this macro is undefined in glibc. The only comment about this flag is in tst-mman-consts.py. It says MAP_UNINITIALIZED is kernel only. Does that mean glibc doesn't support Linux only features? I am not sure. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-02-28 17:59 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-28 17:59 stefan.smorra at gmail dot com [this message] 2024-02-28 18:09 ` [Bug libc/31430] " stefan.smorra at gmail dot com 2024-02-28 18:18 ` schwab@linux-m68k.org 2024-03-01 15:54 ` stefan.smorra at gmail dot com 2024-03-01 18:08 ` schwab@linux-m68k.org 2024-03-01 20:40 ` stefan.smorra at gmail dot com 2024-03-01 20:42 ` stefan.smorra at gmail 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-31430-131@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).