From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
"Luck, Tony" <tony.luck@intel.com>,
"frank.scheiner@web.de" <frank.scheiner@web.de>,
"jrtc27@jrtc27.com" <jrtc27@jrtc27.com>,
"slyfox@gentoo.org" <slyfox@gentoo.org>,
"matorola@gmail.com" <matorola@gmail.com>
Subject: Re: "mm/vmalloc: Add flag for freeing of special permsissions" broke udev on ia64
Date: Wed, 12 Aug 2020 04:50:17 +0000 [thread overview]
Message-ID: <8ae8c65f4c66dbb4469939963741801c24ce22ce.camel@intel.com> (raw)
In-Reply-To: <460f2393-8603-cbda-9bab-4bd24d0c41ed@physik.fu-berlin.de>
On Tue, 2020-08-11 at 23:54 +0200, John Paul Adrian Glaubitz wrote:
> Hi Rick!
>
> I have been bisecting some regressions on ia64 and one problem I ran
> into is that
> udev is causing the kernel to crash after the following change from
> 2019:
>
> commit 868b104d7379e28013e9d48bdd2db25e0bdcf751
> Author: Rick Edgecombe <rick.p.edgecombe@intel.com>
> Date: Thu Apr 25 17:11:36 2019 -0700
>
> mm/vmalloc: Add flag for freeing of special permsissions
>
> With your patch applied, udev crashes on ia64 when trying to load
> modules, I'm pasting
> the whole boot message sequence below.
>
> Any idea what could cause this problem on ia64?
>
> Thanks,
> Adrian
>
Hi,
On non-x86, this patchset shouldn't have changed much, just always
flush the TLB and purge the vmalloc area in cases where previously this
would only happen intermittently. Despite this, it also caused a
problem on sparc. In the end the sparc issue turned out to be an issue
with sparc's kernel range TLB flush implementation that was just now
being hit earlier during boot instead of after the system had been up
for some time. So I'm at first wondering if there might be something
like that uncovered here.
Unfortunately, it's unlikely that I can get access to ia64 hardware in
the near term to debug. Would you be able to test some debug patches?
Also, can you post your config?
Thanks,
Rick
next prev parent reply other threads:[~2020-08-12 4:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 21:54 John Paul Adrian Glaubitz
2020-08-12 4:50 ` Edgecombe, Rick P [this message]
2020-08-12 6:28 ` John Paul Adrian Glaubitz
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=8ae8c65f4c66dbb4469939963741801c24ce22ce.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=frank.scheiner@web.de \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jrtc27@jrtc27.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matorola@gmail.com \
--cc=slyfox@gentoo.org \
--cc=tony.luck@intel.com \
/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