From: Joerg Roedel <jroedel@suse.de>
To: kernel test robot <lkp@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
LKP <lkp@lists.01.org>
Subject: Re: 0604a4fd53 ("x86/mm: remove vmalloc faulting"): [ 80.661587] BUG: unable to handle page fault for address: fb40c000
Date: Thu, 28 May 2020 20:48:57 +0200 [thread overview]
Message-ID: <20200528184857.GE6857@suse.de> (raw)
In-Reply-To: <20200528084208.GV12456@shao2-debian>
Hi,
On Thu, May 28, 2020 at 04:42:09PM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>
> commit 0604a4fd53020a98f029e7fd56d896a136ff2357
> Author: Joerg Roedel <jroedel@suse.de>
> AuthorDate: Sat May 16 15:19:37 2020 +1000
> Commit: Stephen Rothwell <sfr@canb.auug.org.au>
> CommitDate: Sat May 16 15:19:37 2020 +1000
Tried to reproduce this today and found another bug in KVM along the
way. But anyway, I wasn't able to reproduce this on latest linux-next.
By looking at the exact commit-id reported above, I found that this
report is a false-positive.
Above commit-id refers to an old version of the patch-set which does not
call arch_sync_kernel_mappings() in map_kernel_range_noflush(). So the
oops comes from missing synchronization there. But that is fixed already
in latest next/master.
Regards,
Joerg
prev parent reply other threads:[~2020-05-28 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 8:42 0604a4fd53 ("x86/mm: remove vmalloc faulting"): [ 80.661587] BUG: unable to handle page fault for address: fb40c000 kernel test robot
2020-05-28 9:14 ` Joerg Roedel
2020-05-28 18:48 ` Joerg Roedel [this message]
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=20200528184857.GE6857@suse.de \
--to=jroedel@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).