From: John David Anglin <dave.anglin@bell.net>
To: Sam James <sam@gentoo.org>
Cc: linux-parisc@vger.kernel.org, hppa@gentoo.org
Subject: Re: Recurring INEQUIVALENT ALIASES issues and userland corruption/crashes
Date: Tue, 12 Apr 2022 08:27:11 -0400 [thread overview]
Message-ID: <cb19a0a0-69b2-ab14-7767-a0cd7bd671b0@bell.net> (raw)
In-Reply-To: <94439119-D2B6-4961-B61D-95784E09798D@gentoo.org>
On 2022-04-12 1:18 a.m., Sam James wrote:
>>> Mar 22 04:19:55 muta.hppa.dev.gentoo.org kernel: INEQUIVALENT ALIASES 0x411ee000 and 0x428c9000 in file bash
>>> ```
>> It seems all these messages result from a single call to flush_dcache_page. Note the sequential behavior of old_addr
>> and addr, and message times.
> FWIW, from Helge's config on 5.10.108 (config changes on my end: just disabling unneeded devices to speed up build), I have the same
> horrible wall:
This change might help:
https://lore.kernel.org/linux-parisc/YlNw8jzP9OQRKvlV@mx3210.localdomain/T/#u
It applies on top of Helge's current for-next tree which is based on 5.18.0-rc1+.
The messages will no longer appear with this patch on c8000/rp34xx. However, the loop corruption
might still occur. If that happens, I think the stall detector will trigger, or maybe some other crash.
The loop is changed to flush all mount points on machines with PA8800 or PA8900 processors as I
believe these CPUs don't support equivalent aliases.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2022-04-12 12:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 17:52 Recurring INEQUIVALENT ALIASES issues and userland corruption/crashes Sam James
2022-03-22 18:14 ` Helge Deller
2022-03-22 18:30 ` John David Anglin
2022-03-22 19:47 ` Sam James
2022-03-22 18:19 ` John David Anglin
2022-03-22 19:37 ` Sam James
2022-03-22 19:52 ` Helge Deller
2022-03-22 20:42 ` Sam James
2022-03-22 21:04 ` John David Anglin
[not found] ` <73bf3336-9207-ba0e-1950-8cb1b7d6adc3@bell.net>
2022-03-22 20:29 ` John David Anglin
2022-03-22 20:43 ` Sam James
2022-03-22 23:59 ` John David Anglin
2022-04-05 21:13 ` John David Anglin
2022-04-12 5:18 ` Sam James
2022-04-12 12:27 ` John David Anglin [this message]
2022-04-12 13:20 ` John David Anglin
2022-04-12 23:45 ` Sam James
2022-04-19 19:52 ` Sam James
2022-04-19 21:29 ` John David Anglin
2022-04-19 21:52 ` James Bottomley
2022-04-20 0:11 ` John David Anglin
2022-04-23 20:33 ` John David Anglin
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=cb19a0a0-69b2-ab14-7767-a0cd7bd671b0@bell.net \
--to=dave.anglin@bell.net \
--cc=hppa@gentoo.org \
--cc=linux-parisc@vger.kernel.org \
--cc=sam@gentoo.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