From: Jarkko Sakkinen <jarkko@kernel.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: David Howells <dhowells@redhat.com>,
keyrings@vger.kernel.org, stable@vger.kernel.org,
Paulo Alcantara <pc@manguebit.org>,
Namjae Jeon <linkinjeon@kernel.org>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Shyam Prasad N <sprasad@microsoft.com>,
Tom Talpey <tom@talpey.com>, Bharath SM <bharathsm@microsoft.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
"open list:COMMON INTERNET FILE SYSTEM CLIENT (CIFS and SMB3)"
<linux-cifs@vger.kernel.org>,
"moderated list:COMMON INTERNET FILE SYSTEM CLIENT (CIFS and
SMB3)" <samba-technical@lists.samba.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:SECURITY SUBSYSTEM"
<linux-security-module@vger.kernel.org>
Subject: Re: [PATCH v4 1/3] KEYS: Expand key->{datalen,quotalen} to unsigned int
Date: Wed, 21 Oct 2026 01:01:47 +0300 [thread overview]
Message-ID: <atfky30OZQ5vsNVs@kernel.org> (raw)
In-Reply-To: <20261020214335.GE699485@google.com>
On Tue, Oct 20, 2026 at 09:43:35PM +0000, Eric Biggers wrote:
> On Tue, Oct 20, 2026 at 11:49:41PM +0300, Jarkko Sakkinen wrote:
> > For any kernel patches I've missed all Sashiko reviews so far and have
> > not taken the feedback into account in anything.
> >
> > There is two issues:
> >
> > 1. I was not subscribed to linux-security-module. I could be and have
> > been but probably when I've changed my list subscriptions at some
> > point otherwise, I happened not to be.
> > 2. Even if I was subscribed to linux-security-module, at least I'd
> > like to get reviews Cc'd that concern my patches or patches
> > sent to me.
> >
> > Now that Eric pointed out Sashiko review I was able to look up this
> > via web browser:
> >
> > https://lore.kernel.org/linux-security-module/20261020174325.2229448-1-jarkko@kernel.org/T/#mccc5900222fdad9d790be343fcec2a32540ed2fb
> >
> > This is somewhat inconvenient though that it responds like that, and
> > not to the review thread.
> >
> > Not actually sure how do you write a Sieve filter that automates
> > relevant-to-me Sashiko emails going into some specific folder but
> > I'm sure that is somehow possible. I guess I'll start by subscribing
> > to linux-security-module.
>
> Well, the keyrings mailing list isn't currently opted into Sashiko
> monitoring or emails. linux-security-modules is opted in, but it's set
> to have the Sashiko emails go to only that list. See
> https://github.com/sashiko-dev/sashiko/blob/main/projects/linux/mailing_lists.toml
>
> ["linux-security-module@vger.kernel.org"]
> reply_to = ["list"]
> positive_review = "all"
>
> (Sashiko defaults to no email, because unfortunately there hasn't yet
> been consensus in the kernel community to enable it everywhere yet.)
>
> keyrings could be opted in by opening a GitHub pull request that edits
> that file. Let me know if you want me to do it.
>
> My preference is what I set the fscrypt and fsverity lists too: enable
> monitoring of the list and emails of issues found to everyone (but not
> the noisy positive reviews, i.e. "It looks great!"):
>
> ["linux-fscrypt@vger.kernel.org"]
> reply_to = ["author", "list", "recipients"]
>
> So for keyrings I suggest we add:
>
> ["keyrings@vger.kernel.org"]
> reply_to = ["author", "list", "recipients"]
>
> Do you agree with that?
Yeah, that would help, thanks :-)
>
> - Eric
Br, Jarkko
next prev parent reply other threads:[~2026-10-20 22:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 17:43 [PATCH v4 0/3] KEYS: rhashtable bug fixes Jarkko Sakkinen
2026-10-20 17:43 ` [PATCH v4 1/3] KEYS: Expand key->{datalen,quotalen} to unsigned int Jarkko Sakkinen
2026-10-20 20:49 ` Jarkko Sakkinen
2026-10-20 20:59 ` Jarkko Sakkinen
2026-10-20 21:43 ` Eric Biggers
2026-10-20 22:01 ` Jarkko Sakkinen [this message]
2026-10-20 17:43 ` [PATCH v4 2/3] KEYS: Reject descriptions larger than KEY_MAX_DESC_SIZE Jarkko Sakkinen
2026-10-20 21:16 ` Jarkko Sakkinen
2026-10-20 21:18 ` Jarkko Sakkinen
2026-10-20 17:43 ` [PATCH v4 3/3] KEYS: Verify the key identity in __key_unlink_begin Jarkko Sakkinen
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=atfky30OZQ5vsNVs@kernel.org \
--to=jarkko@kernel.org \
--cc=bharathsm@microsoft.com \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=pc@manguebit.org \
--cc=ronniesahlberg@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=serge@hallyn.com \
--cc=sprasad@microsoft.com \
--cc=stable@vger.kernel.org \
--cc=tom@talpey.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 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®