Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From:   Qian Cai <cai@lca.pw>
Mime-Version: 1.0 (1.0)
Subject: Re: linux-next: not-present page at swap_vma_readahead()
Date:   Tue, 14 Apr 2020 22:12:55 -0400
Message-Id: <A6843BF5-6B4C-4A75-B68B-133E8FC77955@lca.pw>
References: <874ktl1p7y.fsf@yhuang-dev.intel.com>
Cc:     Linux-MM <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>,
        Minchan Kim <minchan@kernel.org>,
        Hugh Dickins <hughd@google.com>,
        Andrew Morton <akpm@linux-foundation.org>
In-Reply-To: <874ktl1p7y.fsf@yhuang-dev.intel.com>
To:     "Huang, Ying" <ying.huang@intel.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


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

Yes, I=E2=80=99ll need to find a quick reproducer first by analyzing the fuz=
zer=E2=80=99s last logs.

>=20
> 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 thr=
ead.=