linux-kernel - Re: powerpc64 kernel panic if you disable CONFIG_PPC_TRANSACTIONAL

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]

Message-ID: <CAKTCnznn8fyziWvZf+iuVq6zDV4hebrREwuKV+6ZTjpTz0D6oA@mail.gmail.com>
Date:   Sun, 17 Dec 2017 09:33:27 +1100
From:   Balbir Singh <bsingharora@...il.com>
To:     Rob Landley <rob@...dley.net>
Cc:     Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)" 
        <linuxppc-dev@...ts.ozlabs.org>,
        Benjamin Herrenschmidt <benh@...nel.crashing.org>,
        Paul Mackerras <paulus@...ba.org>,
        Michael Ellerman <mpe@...erman.id.au>
Subject: Re: powerpc64 kernel panic if you disable CONFIG_PPC_TRANSACTIONAL_MEM?

On Sun, Dec 17, 2017 at 8:34 AM, Rob Landley <rob@...dley.net> wrote:
> I just added a ppc64 target to https://github.com/landley/mkroot which
> means I built 4.14 with the attached miniconfig and ran it with the
> attached qemu command line, and it works fine as is but if you remove
> the transactional mem line from the config the kernel panics instead
> of launching a shell prompt:
>
> init[1]: unhandled signal 4 at 0000000010001a04 nip 0000000010001a04
> lr 000000001002ebe8 code 1
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
>

what does the instruction at 10001a04 look like?

Balbir Singh.