linux-kernel - Re: kasan behavior when built with unsupported compiler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5163c242-4bbe-7fec-ab58-9c360abf0afd@virtuozzo.com>
Date:   Thu, 9 Mar 2017 14:23:30 +0300
From:   Andrey Ryabinin <aryabinin@...tuozzo.com>
To:     Dmitry Vyukov <dvyukov@...gle.com>,
        Nikolay Borisov <n.borisov.lkml@...il.com>
CC:     Alexander Potapenko <glider@...gle.com>,
        LKML <linux-kernel@...r.kernel.org>,
        kasan-dev <kasan-dev@...glegroups.com>,
        Kees Cook <keescook@...gle.com>
Subject: Re: kasan behavior when built with unsupported compiler

On 03/09/2017 01:16 PM, Dmitry Vyukov wrote:
> 
> Looking at this report I don't see how this is OOB.
> Object starts at 0xffff88006a2255e0, object size is 69 bytes (from shadow).
> ffff88006a22560e + 20 bytes is not OOB.
> 

Indeed, perhaps gcc 4.7.4 miscompiles something check_memory_region ?
That's the only reasonable explanation I have.