public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Arjun Shankar <arjun.is@lostca.se>
Cc: Paul Eggert <eggert@cs.ucla.edu>, libc-alpha@sourceware.org
Subject: Re: [PATCH] Fix integer overflows in internal memalign and malloc functions [BZ #22343]
Date: Tue, 16 Jan 2018 21:00:00 -0000	[thread overview]
Message-ID: <4976edfa-7e4d-04c5-b451-f1b2c02f7c5a@redhat.com> (raw)
In-Reply-To: <20180116162714.GA36913@aloka.lostca.se>

On 01/16/2018 08:27 AM, Arjun Shankar wrote:
> I vote that we consider reviewing and checking in my original attempt at a
> fix prior to the 2.27 release, and in lieu of this we file a separate bug to
> track the removal of technical debt that already exists in the code. I'll be
> happy to take Paul's patch and run with it once master opens for development
> again.

I think an immediate fix is the right solution for 2.27, these overflows in
malloc are bad.

-- 
Cheers,
Carlos.

  reply	other threads:[~2018-01-16 21:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 17:02 Arjun Shankar
2018-01-04 17:20 ` Zack Weinberg
2018-01-04 20:32 ` Paul Eggert
2018-01-04 23:07   ` Carlos O'Donell
2018-01-16 16:27     ` Arjun Shankar
2018-01-16 21:00       ` Carlos O'Donell [this message]
2018-01-17  6:27         ` Paul Eggert
2018-01-17 14:59           ` Carlos O'Donell
2018-01-16 22:31 ` Carlos O'Donell
2018-01-16 22:56   ` Carlos O'Donell
2018-01-17 20:26 Arjun Shankar
2018-01-17 20:52 ` Florian Weimer
2018-01-17 21:47   ` Carlos O'Donell
2018-01-18  8:04     ` Florian Weimer
2018-01-19  8:32       ` Carlos O'Donell
2018-01-17 22:01 ` Carlos O'Donell

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=4976edfa-7e4d-04c5-b451-f1b2c02f7c5a@redhat.com \
    --to=carlos@redhat.com \
    --cc=arjun.is@lostca.se \
    --cc=eggert@cs.ucla.edu \
    --cc=libc-alpha@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).