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
Subject: Re: [PATCH v2 ] devcoredump : Serialize devcd_del work
Date: Wed, 27 Apr 2022 13:58:25 +0200 [thread overview]
Message-ID: <b3afca400cb3c822164daa9f839eeb443675a4da.camel@sipsolutions.net> (raw)
In-Reply-To: <202204261421.A58121A53E@keescook>
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
prev parent reply other threads:[~2022-04-27 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 13:09 Mukesh Ojha
2022-04-25 14:06 ` Greg KH
2022-04-25 17:00 ` Thomas Gleixner
2022-04-25 17:19 ` Johannes Berg
2022-04-25 19:37 ` Thomas Gleixner
2022-04-26 14:04 ` Mukesh Ojha
2022-04-26 21:25 ` Kees Cook
2022-04-27 11:58 ` Johannes Berg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b3afca400cb3c822164daa9f839eeb443675a4da.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mojha@quicinc.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®