public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31968] mremap implementation in C does not handle arguments correctly
Date: Tue, 09 Jul 2024 13:57:40 +0000 [thread overview]
Message-ID: <bug-31968-131-wOLV3wYKNm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31968-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31968
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |security-
Assignee|unassigned at sourceware dot org |fweimer at redhat dot com
CC| |fweimer at redhat dot com
Status|NEW |ASSIGNED
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-07-09 13:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 13:57 [Bug libc/31968] New: " fweimer at redhat dot com
2024-07-09 13:57 ` fweimer at redhat dot com [this message]
2024-07-09 13:58 ` [Bug libc/31968] " fweimer at redhat dot com
2024-07-09 15:01 ` fweimer at redhat dot com
2024-07-09 22:13 ` hjl.tools at gmail dot com
2024-07-11 3:21 ` hjl.tools at gmail dot com
2024-07-12 22:38 ` hjl.tools at gmail dot com
2024-07-12 22:39 ` hjl.tools at gmail dot com
2024-08-01 12:10 ` cvs-commit at gcc dot gnu.org
2024-08-01 12:38 ` cvs-commit at gcc dot gnu.org
2024-08-01 12:39 ` cvs-commit at gcc dot gnu.org
2024-08-01 13:00 ` cvs-commit at gcc dot gnu.org
2024-08-01 15:15 ` cvs-commit at gcc dot gnu.org
2024-08-01 15:16 ` cvs-commit at gcc dot gnu.org
2024-08-01 15:30 ` cvs-commit at gcc dot gnu.org
2024-09-06 14:33 ` 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-31968-131-wOLV3wYKNm@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: 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).