linux-kernel - Re: linux-next: not-present page at swap_vma

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <A6843BF5-6B4C-4A75-B68B-133E8FC77955@lca.pw>
Date:   Tue, 14 Apr 2020 22:12:55 -0400
From:   Qian Cai <cai@....pw>
To:     "Huang, Ying" <ying.huang@...el.com>
Cc:     Linux-MM <linux-mm@...ck.org>, LKML <linux-kernel@...r.kernel.org>,
        Minchan Kim <minchan@...nel.org>,
        Hugh Dickins <hughd@...gle.com>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: linux-next: not-present page at swap_vma_readahead()



> On Apr 14, 2020, at 10:01 PM, Huang, Ying <ying.huang@...el.com> wrote:
> 
> Is it possible to bisect this?

Yes, I’ll need to find a quick reproducer first by analyzing the fuzzer’s last logs.

> 
> Because the crash point is identified, it may be helpful to collect and
> analyze the status of the faulting page table and readahead ptes.  But I
> am not familiar with the ARM64 architecture.  So I cannot help much
> here.

It happens for x86 as well where the trace is in the first email of this thread.