From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkft-triage@lists.linaro.org,
Andrew Morton <akpm@linux-foundation.org>,
Ira Weiny <ira.weiny@intel.com>,
Oliver Sang <oliver.sang@intel.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
X86 ML <x86@kernel.org>, Kalesh Singh <kaleshsingh@google.com>
Subject: Re: BUG: unable to handle page fault for address - EIP: __kmap_local_page_prot
Date: Thu, 20 May 2021 12:40:11 +0530 [thread overview]
Message-ID: <CA+G9fYsogFQZSeFyGinZ_EQOEW11cmU5oxuEoDuwyCVNaXv3yA@mail.gmail.com> (raw)
In-Reply-To: <87mtsqd0c1.ffs@nanos.tec.linutronix.de>
On Thu, 20 May 2021 at 00:20, Thomas Gleixner <tglx@linutronix.de> wrote:
>
> On Wed, May 19 2021 at 20:38, Naresh Kamboju wrote:
> > While running LTP mm test suite on i386 kernel the following warning and BUG
> > reported on linux next 5.13.0-rc2-next-20210519.
> >
> > The warning is not regression, We have been noticing these warnings often on
> > i386
>
> Noticing? Did you report them?
I have reported this,
https://lore.kernel.org/linux-mm/CA+G9fYt+6OeibZMD0fP=O3nqFbcN3O4xcLkjq0mpQbZJ2uxB9w@mail.gmail.com/
>
> > but kernel BUG: looks to be a new crash.
>
> It's just the consequence of the problem which is pointed out by the
> warning. Fix below.
The below patch did not solve the reported problem.
after applying this patch
CONFIG_HAVE_MOVE_PUD
disappeared from the config.
but still i see WARNING: and BUG: when running LTP mm tests.
Test log link,
FYI,
i386 kernel Image running on x86_64 machine.
https://lkft.validation.linaro.org/scheduler/job/2749690#L10139
> Thanks,
>
> tglx
> ---
> Subject: x86: Don't enable CONFIG_MOVE_PUD for 32bit and !PAE
> From: Thomas Gleixner <tglx@linutronix.de>
> Date: Wed, 19 May 2021 20:37:34 +0200
>
> MOVE_PUD cannot work for 2-level paging obviously.
>
> Fixes: be37c98d1134 ("x86: mremap speedup - Enable HAVE_MOVE_PUD")
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: Kalesh Singh <kaleshsingh@google.com>
> Cc: stable@vger.kernel.org
> ---
> arch/x86/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -219,7 +219,7 @@ config X86
> select HAVE_MIXED_BREAKPOINTS_REGS
> select HAVE_MOD_ARCH_SPECIFIC
> select HAVE_MOVE_PMD
> - select HAVE_MOVE_PUD
> + select HAVE_MOVE_PUD if PGTABLE_LEVELS > 2
> select HAVE_NMI
> select HAVE_OPTPROBES
> select HAVE_PCSPKR_PLATFORM
- Naresh
next prev parent reply other threads:[~2021-05-20 7:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 15:08 BUG: unable to handle page fault for address - EIP: __kmap_local_page_prot Naresh Kamboju
2021-05-19 15:31 ` Matthew Wilcox
[not found] ` <87mtsqd0c1.ffs@nanos.tec.linutronix.de>
2021-05-19 19:22 ` Peter Zijlstra
2021-05-20 7:10 ` Naresh Kamboju [this message]
2021-05-20 12:51 ` Thomas Gleixner
2021-05-20 13:04 ` Naresh Kamboju
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=CA+G9fYsogFQZSeFyGinZ_EQOEW11cmU5oxuEoDuwyCVNaXv3yA@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=akpm@linux-foundation.org \
--cc=ira.weiny@intel.com \
--cc=kaleshsingh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkft-triage@lists.linaro.org \
--cc=oliver.sang@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).