linux-kernel - Re: (subset) [PATCH 7/8] efi: pstore: Follow convention for the efi-pstore backend name

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: <166576925933.1456464.15444113469951956884.b4-ty@chromium.org>
Date:   Fri, 14 Oct 2022 10:41:04 -0700
From:   Kees Cook <keescook@...omium.org>
To:     gpiccoli@...lia.com, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org
Cc:     Kees Cook <keescook@...omium.org>, ardb@...nel.org,
        linux-efi@...r.kernel.org, anton@...msg.org,
        Tony Luck <tony.luck@...el.com>, ccross@...roid.com,
        kernel-dev@...lia.com, kernel@...ccoli.net
Subject: Re: (subset) [PATCH 7/8] efi: pstore: Follow convention for the efi-pstore backend name

On Thu, 6 Oct 2022 19:42:11 -0300, Guilherme G. Piccoli wrote:
> For some reason, the efi-pstore backend name (exposed through the
> pstore infrastructure) is hardcoded as "efi", whereas all the other
> backends follow a kind of convention in using the module name.
> 
> Let's do it here as well, to make user's life easier (they might
> use this info for unloading the module backend, for example).
> 
> [...]

Applied to for-next/pstore, thanks!

[7/8] efi: pstore: Follow convention for the efi-pstore backend name
      https://git.kernel.org/kees/c/39bae0ee0656

-- 
Kees Cook