From: Jakub Wilk <jwilk@jwilk.net>
To: Jann Horn <jannh@google.com>
Cc: Alejandro Colomar <alx@kernel.org>,
linux-man@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org
Subject: Re: [PATCH man] mmap.2: Document danger of mappings larger than PTRDIFF_MAX
Date: Wed, 9 Apr 2025 22:25:48 +0200 [thread overview]
Message-ID: <20250409202548.unp4btmb7ktq2igk@jwilk.net> (raw)
In-Reply-To: <20250409200316.1555164-1-jannh@google.com>
* Jann Horn <jannh@google.com>, 2025-04-09 22:03:
> - glibc malloc restricts object size to <=PTRDIFF_MAX in
> checked_request2size()
FWIW, this is done only since glibc v2.30 (released in 2019):
https://sourceware.org/cgit/glibc/commit/?id=9bf8e29ca136094f
--
Jakub Wilk
next prev parent reply other threads:[~2025-04-09 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 20:03 Jann Horn
2025-04-09 20:25 ` Jakub Wilk [this message]
2025-04-09 20:41 ` Alejandro Colomar
2025-04-10 18:08 ` Jann Horn
2025-04-10 20:30 ` Alejandro Colomar
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=20250409202548.unp4btmb7ktq2igk@jwilk.net \
--to=jwilk@jwilk.net \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alx@kernel.org \
--cc=jannh@google.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=vbabka@suse.cz \
/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