linux-kernel - Re: [Question PATCH 0/1] mm: crash in vmalloc_to_page

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: <921e8bb3-3c4d-be75-3029-35fde00087c7@huawei.com>
Date:   Fri, 2 Mar 2018 15:23:45 +0200
From:   Igor Stoppa <igor.stoppa@...wei.com>
To:     <mhocko@...nel.org>
CC:     <willy@...radead.org>, <linux-mm@...ck.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [Question PATCH 0/1] mm: crash in vmalloc_to_page - misuse or
 bug?

Ping?

The kernel test automation seems to confirm my findings:

https://marc.info/?l=linux-mm&m=151999308428656&w=2

Is this really a bug?

On 22/02/18 16:13, Igor Stoppa wrote:
> While trying to change the code of find_vm_area, I got an automated
> notification that my code was breaking the testing of i386, based on the
> 0-day testing automation from 01.org
> 
> I started investigating the issue and noticed that it seems to be
> reproducible also on top of plain 4.16-rc2, without any of my patches.
> 
> I'm still not 100% sure that I'm doing something sane, but I thought it
> might be good to share the finding.
> 
> The patch contains both a minimal change, to trigger the crash, and a
> snippet of the log of the crash i get.
> 
> Igor Stoppa (1):
>   crash vmalloc_to_page()
> 
>  mm/vmalloc.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)


--
igor