From: Roman Gushchin <roman.gushchin@linux.dev>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: "Paul Moore" <paul@paul-moore.com>,
linux-security-module@vger.kernel.org, sashiko@lists.linux.dev,
"Günther Noack" <gnoack3000@gmail.com>
Subject: Re: Sashiko reviews for the LSM mailing list
Date: Tue, 16 Jun 2026 23:05:39 +0000 [thread overview]
Message-ID: <7ia4v7biqe64.fsf@castle.c.googlers.com> (raw)
In-Reply-To: <20260616.aiGaim8xie8z@digikod.net> ("Mickaël Salaün"'s message of "Tue, 16 Jun 2026 16:59:03 +0200")
Mickaël Salaün <mic@digikod.net> writes:
> On Tue, Jun 16, 2026 at 10:11:42AM -0400, Paul Moore wrote:
>> On Tue, Jun 16, 2026 at 4:49 AM Mickaël Salaün <mic@digikod.net> wrote:
>> > On Mon, Jun 15, 2026 at 04:13:59PM -0400, Paul Moore wrote:
>> > > On Mon, Jun 15, 2026 at 11:41 AM Mickaël Salaün <mic@digikod.net> wrote:
>> > > >
>> > > > Hi,
>> > > >
>> > > > I've been reading Sashiko's (AI bot) reviews wrt Landlock patches, and
>> > > > most of them were valuable. It found issues (security or not), but it
>> > > > requires to go to https://sashiko.dev to find them, which is too easy to
>> > > > forget, and requires additional work from maintainers to copy or point
>> > > > to these reviews. I sent a PR (currently in draft) to enable email
>> > > > replies from Sashiko to the Linux Security Module mailing list (most
>> > > > patches are already reviewed anyway):
>> > > > https://github.com/sashiko-dev/sashiko/pull/278
>> > > >
>> > > > Making such reviews broadly available can improve the quality of patches
>> > > > we receive without much noise, helping for all LSM-related code. We can
>> > > > fine tune some email-related settings if needed.
>> > > >
>> > > > If there are any concern or question, this is the right time to start a
>> > > > discussion.
>> > >
>> > > I recently enabled Sashiko for the SELinux list to trial it there
>> > > first, with the goal of eventually bringing this topic up for the rest
>> > > of the LSM folks on the LSM list.
>> > >
>> > > While I think Sashiko's review comments are generally okay, you should
>> > > have contacted the LSM mailing list folks *before* submitting a PR
>> > > that would cause an automated bot to send email to the LSM list (this
>> > > applies to all automated emails, not just LLM reviews). Please hold
>> > > the PR until you have given people a chance to comment on the issue.
>> >
>> > As I explained just above, the PR is a draft (GitHub specific state for
>> > WIP), so it cannot be merged as-is, but it is useful for reviews and for
>> > LSM folks to get a look if they are interested.
>> >
>> > > Personally, I'm okay with it.
>> >
>> > Looks good. What about waiting a week to get some feedback here and
>> > then ask for a merge of the PR?
>>
>> I would suggest enabling Sashiko for the LSM list, but not enabling
>> the email replies at first. This would allow people to view the
>> reviews and perhaps make a better informed decision.
I just did this: 611f4cd410d9a7f7ad923a068a6ced455e3a244e , for enabling
reviews I don't really need maintainers consensus. (I might roll it out
a bit later)
But when it comes to email policy I do, so I'll just sit and wait here.
Thanks
next prev parent reply other threads:[~2026-06-16 23:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 15:37 Sashiko reviews for the LSM mailing list Mickaël Salaün
2026-06-15 20:13 ` Paul Moore
2026-06-16 8:49 ` Mickaël Salaün
2026-06-16 14:11 ` Paul Moore
2026-06-16 14:59 ` Mickaël Salaün
2026-06-16 15:23 ` Paul Moore
2026-06-16 19:03 ` Mickaël Salaün
2026-06-16 23:05 ` Roman Gushchin [this message]
2026-06-17 2:20 ` Paul Moore
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=7ia4v7biqe64.fsf@castle.c.googlers.com \
--to=roman.gushchin@linux.dev \
--cc=gnoack3000@gmail.com \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
--cc=sashiko@lists.linux.dev \
/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