From: "Huang\, Ying" <ying.huang@intel.com>
To: Qian Cai <cai@lca.pw>
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>
Subject: Re: linux-next: not-present page at swap_vma_readahead()
Date: Wed, 15 Apr 2020 16:54:08 +0800 [thread overview]
Message-ID: <875ze1yvrj.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <A6843BF5-6B4C-4A75-B68B-133E8FC77955@lca.pw> (Qian Cai's message of "Tue, 14 Apr 2020 22:12:55 -0400")
Qian Cai <cai@lca.pw> writes:
>> On Apr 14, 2020, at 10:01 PM, Huang, Ying <ying.huang@intel.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.
Can you share the reproducer to me when it's available? Or the command
line you used to reproduce it now?
>>
>> 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.
Got it! Thanks!
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2020-04-15 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 14:32 linux-next: not-present page at swap_vma_readahead() Qian Cai
2020-04-14 21:22 ` Qian Cai
2020-04-15 2:01 ` Huang, Ying
2020-04-15 2:12 ` Qian Cai
2020-04-15 8:54 ` Huang, Ying [this message]
2020-04-15 13:11 ` Qian Cai
2020-06-16 1:13 ` Qian Cai
2020-07-20 0:37 ` Huang, Ying
2020-07-20 2:12 ` Qian Cai
2020-07-20 3:32 ` Huang, Ying
2020-07-20 3:54 ` Qian Cai
2020-07-20 4:37 ` Huang, Ying
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875ze1yvrj.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.