linux-kernel - Re: [Xen-devel] [PATCH] x86/xen: Return from panic notifier

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 for Android: free password hash cracker in your pocket

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

Message-ID: <9d6b6b00-a3b1-95b4-7633-597c0094ab90@oracle.com>
Date:   Wed, 2 Oct 2019 10:14:54 -0400
From:   Boris Ostrovsky <boris.ostrovsky@...cle.com>
To:     Jan Beulich <jbeulich@...e.com>
Cc:     james@...gwall.me.uk, xen-devel@...ts.xenproject.org,
        Juergen Gross <jgross@...e.com>, linux-kernel@...r.kernel.org
Subject: Re: [Xen-devel] [PATCH] x86/xen: Return from panic notifier

On 10/2/19 9:42 AM, Jan Beulich wrote:
>
> I can only guess that the thinking probably was that e.g. external
> dumping (by the tool stack) would be more reliable (including but
> not limited to this meaning less change of state from when the
> original crash reason was detected) than having the domain dump
> itself.

We could register an external dumper (controlled by a boot option
perhaps, off by default) that will call directly into hypervisor with
SHUTDOWN_crash. That will guarantee that we will complete the notifier
chain without relying on priorities. (Of course this still won't address
a possible new feature in panic() that might be called post-dumping)

If you think it's worth doing this can be easily added.

-boris

> True. I guess more control over the behavior needs to be given to
> the admin, as either approach has its up- and downsides
>