Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Message-ID: <b3afca400cb3c822164daa9f839eeb443675a4da.camel@sipsolutions.net>
Subject: Re: [PATCH v2 ] devcoredump : Serialize devcd_del work
From:   Johannes Berg <johannes@sipsolutions.net>
To:     Kees Cook <keescook@chromium.org>,
        Mukesh Ojha <quic_mojha@quicinc.com>
Cc:     Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org,
        sboyd@kernel.org, rafael@kernel.org, gregkh@linuxfoundation.org
Date:   Wed, 27 Apr 2022 13:58:25 +0200
In-Reply-To: <202204261421.A58121A53E@keescook>
References: <87levt14kn.ffs@tglx>
         <8186de033c87f0cdec296ae272a72c5b9a2880a3.camel@sipsolutions.net>
         <878rrt0xa2.ffs@tglx> <13df1664-fc52-4772-afa1-4f75019b7830@quicinc.com>
         <202204261421.A58121A53E@keescook>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

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