From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24759 invoked by alias); 16 Jan 2013 10:38:19 -0000 Received: (qmail 23982 invoked by uid 48); 16 Jan 2013 10:38:02 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/55975] FAIL: c-c++-common/asan/global-overflow-1.c -O0 output pattern test Date: Wed, 16 Jan 2013 10:38:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2013-01/txt/msg01492.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55975 --- Comment #5 from Jakub Jelinek 2013-01-16 10:38:01 UTC --- Sounds like a recent change: http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=commitdiff;h=048ee0993ec8360abb0b51bdf8f8721e9ed62ec4 The question is what to do about that on the libasan side. Can we keep + (1ULL << 41) asan_shadow_offset for both 44-bit and 46-bit user address spaces? If we just increase kHighMemEnd to 0x00003fffffffffffUL, it will mean that on older kernels half of the user address space will be the shadow memory (from 0x20000000000 to 0x9ffffffffff). Perhaps that is still acceptable, but if ever the address space grows again, we'd need to make size of shadow memory region and kHighMemEnd dynamic.