From: Jarkko Sakkinen <jarkko@kernel.org>
To: eee sss <eeesssooo020@gmail.com>
Cc: David Howells <dhowells@redhat.com>,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: [PATCH] keys: Pin request_key_auth payload in instantiate paths
Date: Sat, 30 May 2026 19:49:57 +0300 [thread overview]
Message-ID: <ahsVNQgmKuTeaAZH@kernel.org> (raw)
In-Reply-To: <ahsUxQryCvPggKBt@kernel.org>
On Sat, May 30, 2026 at 07:48:10PM +0300, Jarkko Sakkinen wrote:
> On Sat, May 30, 2026 at 09:19:33AM -0700, eee sss wrote:
> > Hi Jarkko,
> >
> > Yes, I have a reproducer available as a tar.gz file.
> >
> > I am not attaching it directly here because I am not sure what the preferred
> > way is to share a tar.gz reproducer in this mail context, especially with
> > mailing lists on Cc. Please let me know whether you would prefer a direct
> > attachment, a private upload location, encrypted transfer, or another channel.
> >
> > BR,
> > Shaomin
>
> Drop it to me as private! I actually have now queue of total three
> reproducers but I'll get to this sometime next week :-) Lots of stuff
> apparently happening in sec.
polite request: it is advicable to use plain text in. It's not just me
whining but also sometimes some ML servers simply drop HTML mail i.e.
only non-ML recipients will get it. Just something to be aware of that's
all.
BR, Jarkko
prev parent reply other threads:[~2026-05-30 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 2:48 [PATCH] keys: Pin request_key_auth payload in instantiate paths Shaomin Chen
2026-05-29 22:53 ` Jarkko Sakkinen
[not found] ` <CA+TOyfhe=0Ty-FQDZy-9_LWJ6dgakzyjog5rNfQ2NdCc5X+dFQ@mail.gmail.com>
2026-05-30 16:48 ` Jarkko Sakkinen
2026-05-30 16:49 ` Jarkko Sakkinen [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=ahsVNQgmKuTeaAZH@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=eeesssooo020@gmail.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.