linux-hardening - Re: [PATCH v2] pstore/blk: Export a method to implemente panic

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] [day] [month] [year] [list]

Message-ID: <Y+NCXyT8EM0G0xU3@infradead.org>
Date:   Tue, 7 Feb 2023 22:34:07 -0800
From:   Christoph Hellwig <hch@...radead.org>
To:     Victor Hassan <victor@...winnertech.com>
Cc:     keescook@...omium.org, tony.luck@...el.com, gpiccoli@...lia.com,
        linux-hardening@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] pstore/blk: Export a method to implemente
 panic_write()

On Mon, Feb 06, 2023 at 02:18:13PM +0800, Victor Hassan wrote:
> The panic_write() is necessary to write the pstore frontend message
> to blk devices when panic. Here is a way to register panic_write when
> we use "best_effort" way to register the pstore blk-backend.

This looks like a really awkware interface.  And without also posting
the users it not only has no chance to ever be merged, but also robs
us of a good way to try to help you to find a better interface.