linux-kernel - Re: [PATCH 5/5] MAINTAINERS: Update pstore maintainers

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]

Date:   Thu, 17 Nov 2022 19:05:05 -0300
From:   "Guilherme G. Piccoli" <gpiccoli@...lia.com>
To:     Kees Cook <keescook@...omium.org>
Cc:     linux-hardening@...r.kernel.org,
        Anton Vorontsov <anton@...msg.org>,
        Colin Cross <ccross@...roid.com>,
        Tony Luck <tony.luck@...el.com>,
        Paramjit Oberoi <pso@...omium.org>,
        Ard Biesheuvel <ardb@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/5] MAINTAINERS: Update pstore maintainers

On 17/11/2022 19:01, Kees Cook wrote:
> [...]
>> PSTORE FILESYSTEM
>> M:      Kees Cook <keescook@...omium.org>
>> [...]
>> F:      include/linux/pstore*
>> K:      \b(pstore|ramoops) <------
>>
>> Should this be kept? Maybe only the ramoops entry could be removed?
> 
> I would like to keep it -- if something mentions pstore and ramoops, I'd
> like to see it. I can't review all of it, but I'd like it to at least
> show up in my inbox. :)
> 

Totally fine by me, was curious and now I understand this is not legacy,
but something of your interest indeed.
Thanks for the prompt response!

Cheers,


Guilherme