linux-kernel - Re: [sparc64] running stress-ng and a sparc64 hardware / kernel woes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 3 Jan 2021 14:10:48 +0100
From:   John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To:     Anatoly Pugachev <matorola@...il.com>,
        Linux Kernel list <linux-kernel@...r.kernel.org>
Cc:     Sparc kernel list <sparclinux@...r.kernel.org>
Subject: Re: [sparc64] running stress-ng and a sparc64 hardware / kernel woes

Hi Anatoly!

On 1/3/21 1:56 PM, Anatoly Pugachev wrote:
> Running a simple stress-ng as a non-privileged (non root) user :
> 
> stress-ng --opcode 1 --timeout 60 --metrics-brief
> 
> will almost always bring the linux kernel to an unusable state,
> starting from "Unable to handle kernel NULL pointer dereference",
> "Bogus kernel PC [0000000000000000] in fault handler", "Kernel
> unaligned access at TPC", "Unable to handle kernel paging request at
> virtual address" and "rcu: INFO: rcu_sched detected stalls on
> CPUs/tasks"...

This looks very similar to the kernel crashes on SPARC that we saw on
the buildds for the GCC testsuite in the past (and other packages).

I wonder whether we can use stress-ng to provoke the kernel crash on
POWER when hosting big-endian VMs with high load on little-endian hosts [1].

Adrian

> [1] https://bugzilla.kernel.org/show_bug.cgi?id=206669

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@...ian.org
`. `'   Freie Universitaet Berlin - glaubitz@...sik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913