linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Joerg, Roedel," <jroedel@suse.de>
To: kernel test robot <lkp@intel.com>
Cc: LKP <lkp@lists.01.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Stephen, Rothwell," <sfr@canb.auug.org.au>,
	philip.li@intel.com
Subject: Re: 0604a4fd53 ("x86/mm: remove vmalloc faulting"):  BUG: unable to handle page fault for address: f8001038
Date: Thu, 4 Jun 2020 09:57:28 +0200	[thread overview]
Message-ID: <20200604075728.GM6857@suse.de> (raw)
In-Reply-To: <5ed869c7.3GpRlu0hrFzKB6an%lkp@intel.com>

Hi,

On Thu, Jun 04, 2020 at 11:25:59AM +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
> 
>     x86/mm: remove vmalloc faulting
>     
>     Remove fault handling on vmalloc areas, as the vmalloc code now takes care
>     of synchronizing changes to all page-tables in the system.

This report is a false positive as the tested commit history does not
contain the fixup for map_kernel_range_noflush() which adds the call to
arch_sync_kernel_mappings() there.


Regards,

	Joerg



      reply	other threads:[~2020-06-04  7:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04  3:25 kernel test robot
2020-06-04  7:57 ` 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=20200604075728.GM6857@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 \
    --cc=philip.li@intel.com \
    --cc=sfr@canb.auug.org.au \
    /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