public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug malloc/28506] malloc-check + malloc_usable_size(NULL) causes segfault Date: Fri, 29 Oct 2021 09:28:50 +0000 [thread overview] Message-ID: <bug-28506-131-xMr3t6gzTY@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28506-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28506 --- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The release/2.34/master branch has been updated by Siddhesh Poyarekar <siddhesh@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=01bffc013cdad1e0c45db7aa57efb2bee61f3338 commit 01bffc013cdad1e0c45db7aa57efb2bee61f3338 Author: Siddhesh Poyarekar <siddhesh@sourceware.org> Date: Fri Oct 29 14:53:55 2021 +0530 Handle NULL input to malloc_usable_size [BZ #28506] Hoist the NULL check for malloc_usable_size into its entry points in malloc-debug and malloc and assume non-NULL in all callees. This fixes BZ #28506 Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org> Reviewed-by: Florian Weimer <fweimer@redhat.com> Reviewed-by: Richard W.M. Jones <rjones@redhat.com> (cherry picked from commit 88e316b06414ee7c944cd6f8b30b07a972b78499) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-29 9:28 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-27 21:03 [Bug malloc/28506] New: malloc-check + malloc_usage_size(NULL) " rjones at redhat dot com 2021-10-27 21:07 ` [Bug malloc/28506] malloc-check + malloc_usable_size(NULL) " rjones at redhat dot com 2021-10-27 21:12 ` schwab@linux-m68k.org 2021-10-28 13:38 ` rjones at redhat dot com 2021-10-29 3:19 ` siddhesh at sourceware dot org 2021-10-29 9:26 ` cvs-commit at gcc dot gnu.org 2021-10-29 9:28 ` cvs-commit at gcc dot gnu.org [this message] 2021-10-29 9:29 ` siddhesh at sourceware dot org
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-28506-131-xMr3t6gzTY@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).