linux-kernel - Re: qemu sparc64 runtime crashes in -next

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:   Wed, 14 Jun 2017 15:31:08 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     linux@...ck-us.net
Cc:     pasha.tatashin@...cle.com, linux-kernel@...r.kernel.org,
        bob.picco@...cle.com, steven.sistare@...cle.com
Subject: Re: qemu sparc64 runtime crashes in -next

From: Guenter Roeck <linux@...ck-us.net>
Date: Wed, 14 Jun 2017 03:13:54 -0700

> Hi,
> 
> my sparc qemu tests started failing with next-20170613.
> Log output is not very helpful:
> 
> Unhandled Exception 0x0000000000000028
> PC = 0x00000000004620f4 NPC = 0x00000000004620f8
> Stopping execution
> 
> It looks like 0x00000000004620f4 is in init_tick_ops().
> 
> Bisect points to commit 'sparc64: improve modularity tick options'.
> Bisect log is attached.
> 
> No idea if this is a qemu problem. If you think it is, anything to
> help
> tracking it down would be appreciated.

Pavel, please look into this.

It looks weird that the commit it bisects to would cause a problem.
Maybe the change from __read_mostly to __cachelin_aligned causes the
issue?

Really weird...