linux-kernel - Re: [PATCH v2 ] devcoredump : Serialize devcd

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: <b3afca400cb3c822164daa9f839eeb443675a4da.camel@sipsolutions.net>
Date:   Wed, 27 Apr 2022 13:58:25 +0200
From:   Johannes Berg <johannes@...solutions.net>
To:     Kees Cook <keescook@...omium.org>,
        Mukesh Ojha <quic_mojha@...cinc.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
        sboyd@...nel.org, rafael@...nel.org, gregkh@...uxfoundation.org
Subject: Re: [PATCH v2 ] devcoredump : Serialize devcd_del work

On Tue, 2022-04-26 at 14:25 -0700, Kees Cook wrote:
> > 
> > https://lore.kernel.org/lkml/1650981343-11739-1-git-send-email-quic_mojha@quicinc.com/
> > 
> > While, we would like to hear from Kees about reason of immediate flush from
> > disabled_store().
> 
> This is lost to ancient history in my brain right now. Do you have any
> references to past threads on this? The only thing I remember about
> device memory dumping was just to make sure that lockdown's
> CONFIDENTIALITY mode would block it.
> 

Hm, no, I don't, sorry. I don't even have an email record of it now,
perhaps it went to my @intel.com and has long expired?

Anyway, I seem to remember you asking to have a disable bit and I
implemented it in commit d45333294da8, which you reviewed, but I have no
record of you asking for it even though I think you did :)

johannes