From: Paul Moore <paul@paul-moore.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Coly Li <colyli@fnnas.com>, Steven Rostedt <rostedt@goodmis.org>,
Jan Kara <jack@suse.cz>,
ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] re-think of richACLs in AI/LLM era
Date: Mon, 8 Sep 2025 21:03:24 -0400 [thread overview]
Message-ID: <CAHC9VhRyRuBtzwn2LbwxqLvj21LwrwrAZx4N3f7At1HHyNFPCQ@mail.gmail.com> (raw)
In-Reply-To: <4f2d4025-9fbf-441d-a51a-0c0d4ba16314@infradead.org>
On Mon, Sep 8, 2025 at 7:23 PM Randy Dunlap <rdunlap@infradead.org> wrote:
> On 9/8/25 8:42 AM, Coly Li wrote:
> >> 2025年9月8日 23:39,Steven Rostedt <rostedt@goodmis.org> 写道:
> >>
> >>>
> >>> I'm not really on program committee for either a Maintainers summit or LPC
> >>> so take this just as a friendly advice from a bystander :)
> >>>
> >>
> >> As Jan has stated, this is a technical topic. But you can send it to this
> >> list too. From Ted's original email:
> >>
> >> Related to the Maintainer's Summit, the Kernel Summit is organized as
> >> a track which is run in parallel with the other tracks at the Linux
> >> Plumbers Conference (LPC), and is open to all registered attendees of
> >> LPC. The goal of the Kernel Summit track will be to provide a forum
> >> to discuss specific technical issues that would be easier to resolve
> >> in person than over e-mail. The program committee will also consider
> >> "information sharing" topics if they are clearly of interest to the
> >> wider development community (i.e., advanced training in topics that
> >> would be useful to kernel developers).
> >>
> >> To suggest a topic for the Kernel Summit, please do two things. by
> >> September 10th, 2025. First, please send e-mail with a subject prefix of
> >> [TECH TOPIC] to ksummit@lists.linux.dev. As before, please use a separate
> >> e-mail for each topic.
> >>
> >> Secondly, please create a topic at the Linux Plumbers Conference
> >> proposal submission site and target it to the Kernel Summit track:
> >>
> >> https://lpc.events/event/19/abstracts
> >>
> >> Please do both steps. I'll try to notice if someone forgets one or
> >> the other, but your chances of making sure your proposal gets the
> >> necessary attention and consideration are maximized by submitting both
> >> to the mailing list and the web site.
> >>
> >>
> >> The CfP is closing this Wednesday, so please submit it soon.
> >
> > Yes, I already submitted the CfP on https://lpc.events/event/19/abstracts and got the confirmation email.
> >
> > Also I resend another proposal email subjected with [TECH TOPIC] and almost identical message body.
> >
> > Thanks for the hint!
>
> Hi,
> I don't object to such a topic, but I thought that LSMs were the wave
> of the future for extended attributes or special capability handling. ?
I can't say I'm familiar with the RichACL concept, but generally
speaking yes, the LSM framework exists as a way to implement access
control mechanisms beyond the traditional Linux access controls (other
things too, but those aren't really relevant here).
--
paul-moore.com
next prev parent reply other threads:[~2025-09-09 1:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 8:33 Coly Li
2025-09-08 10:52 ` Jan Kara
2025-09-08 13:47 ` Coly Li
2025-09-08 15:39 ` Steven Rostedt
2025-09-08 15:42 ` Coly Li
2025-09-08 23:22 ` Randy Dunlap
2025-09-09 1:03 ` Paul Moore [this message]
2025-09-10 13:32 ` Coly Li
2025-09-10 19:11 ` Paul Moore
2025-09-16 17:12 ` Coly Li
2025-09-16 18:07 ` Randy Dunlap
2025-09-17 7:59 ` Jan Kara
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=CAHC9VhRyRuBtzwn2LbwxqLvj21LwrwrAZx4N3f7At1HHyNFPCQ@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=colyli@fnnas.com \
--cc=jack@suse.cz \
--cc=ksummit@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
/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