mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-stable <stable@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	lkft-triage@lists.linaro.org,
	"open list:KERNEL SELFTEST FRAMEWORK" 
	<linux-kselftest@vger.kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>, Shuah Khan <shuah@kernel.org>
Subject: Re: selftests: arm64: fp-stress: Unable to handle kernel paging request at virtual address
Date: Tue, 7 Nov 2023 14:21:04 +0000	[thread overview]
Message-ID: <ZUpH0FNTYAl9Z+L6@finisterre.sirena.org.uk> (raw)
In-Reply-To: <CA+G9fYsrLTbFkz-LJmAY9efDyEr-8bHcxivBDPToPjBxjStoDg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2258 bytes --]

On Tue, Nov 07, 2023 at 06:43:25PM +0530, Naresh Kamboju wrote:

> # # SVE-VL-64-0: Expected
> [3904000039044000390480003904c0003904000139044001390480013904c0013904000239044002390480023904c0023904000339044003390480033904c003]
> <>

You've elided *lots* of error reports from the actual test which suggest
that there is substantial memory corruption, it looks like tearing part
way through loading or saving the values - the start of the vectors
looks fine but at some point they get what looks like a related process'
data, eg:

# # SVE-VL-64-0: 	Expected [3904000039044000390480003904c0003904000139044001390480013904c0013904000239044002390480023904c0023904000339044003390480033904c003]
# # SVE-VL-64-0: 	Got      [3904000039044000390480003904c000390480003904c00039040001390440013904000139044001390480013904c001390480013904c0013904000239044002]

This only appears to affect SVE and SME, I didn't spot any FPSIMD
corruption but then that is the smallest case (and I didn't notice any
VL 16 cases either).  It looks like the corruption is on the first thing
we check each time (either register 0 or the highest ZA.H vector for
ZA), all the values do look lke they were plausibly generated by
fp-stress test programs.

Then we get what looks like memory corruption:

> # # SVE-VL-256-<1>[   88.160313] Unable to handle kernel paging
> request at virtual address 00550f0344550f02

> <4>[   88.195706] Call trace:
> <4>[ 88.196098] percpu_ref_get_many
> (include/linux/percpu-refcount.h:174 (discriminator 2)
> include/linux/percpu-refcount.h:204 (discriminator 2))
> <4>[ 88.196815] refill_obj_stock (mm/memcontrol.c:3339 (discriminator 2))
> <4>[ 88.197367] obj_cgroup_uncharge (mm/memcontrol.c:3406)
> <4>[ 88.197835] kmem_cache_free (include/linux/mm.h:1630
> include/linux/mm.h:1849 include/linux/mm.h:1859 mm/slab.h:208
> mm/slab.h:572 mm/slub.c:3804 mm/slub.c:3831)
> <4>[ 88.198407] put_pid.part.0 (kernel/pid.c:118)
> <4>[ 88.198870] delayed_put_pid (kernel/pid.c:127)
> <4>[ 88.200527] rcu_core (arch/arm64/include/asm/preempt.h:13
> (discriminator 1) kernel/rcu/tree.c:2146 (discriminator 1)
> kernel/rcu/tree.c:2403 (discriminator 1))

This all seems very surprising, especially given that AFAICT there are
no changes in stable-6.6-rc for arch/arm64.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-11-07 14:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 13:13 Naresh Kamboju
2023-11-07 14:21 ` Mark Brown [this message]
2023-11-07 14:44   ` Naresh Kamboju
2023-11-07 16:05     ` Mark Brown
2023-11-07 17:10       ` Naresh Kamboju
  -- strict thread matches above, loose matches on Subject: below --
2023-11-07 13:02 Naresh Kamboju
2023-11-07 13:04 ` Naresh Kamboju
2023-11-07 13:30 ` Catalin Marinas

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=ZUpH0FNTYAl9Z+L6@finisterre.sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=sashal@kernel.org \
    --cc=shuah@kernel.org \
    --cc=stable@vger.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

all inboxes | Powered by JetHome®