From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 4B5B83894E61; Mon,  4 May 2020 21:48:04 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4B5B83894E61
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1588628884;
 bh=tFgdC5SQ4Sb79mU/iUObjZE5/R9k7ZauA0vtqfhMQCc=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=TyFVXfgfHHQr04vJpecvn1stJ9tANy0y8jURsFwkpfjHzOi8Xqfw9pwbgQiR588iG
 aW2yabDaNtAO2Gudw67Pl7kt1m2QZyDNwvuHrVp2zFTdbwMowxj3QLafQ/TrPOe6mZ
 zXdMpyrOU0/kpHkpRq5RdNuzSsM4d7V88s0kQn3Y=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/94906] memory corruption in
 std::pmr::monotonic_buffer_resource
Date: Mon, 04 May 2020 21:48:04 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-94906-4-HQmoZDlhlG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-94906-4@http.gcc.gnu.org/bugzilla/>
References: <bug-94906-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 04 May 2020 21:48:04 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94906

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:bb27781b64162e1769df15e0c97e8d2145d2d10d

commit r11-53-gbb27781b64162e1769df15e0c97e8d2145d2d10d
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon May 4 21:13:28 2020 +0100

    libstdc++: Fix incorrect size calculation in PMR resource  (PR 94906)

    Calculating the size of a chunk being returned to the upstream allocator
    was done with a 32-bit type, so it wrapped if the chunk was 4GB or
    larger.

    I don't know how to test this without allocating 4GB, so there's no test
    in the testsuite. It has been tested manually with allocations sizes and
    alignments exceeding 4GB.

            PR libstdc++/94906
            * src/c++17/memory_resource.cc
            (monotonic_buffer_resource::_Chunk::release): Use size_t for sh=
ift
            operands.=