All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dr. Greg" <greg@enjellic.com>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-security-module@vger.kernel.org, roberto.sassu@huaweicloud.com
Subject: Re: [PATCH] Do not require attributes for security_inode_init_security.
Date: Sat, 30 Mar 2024 09:46:04 -0500	[thread overview]
Message-ID: <20240330144604.GA4625@wind.enjellic.com> (raw)
In-Reply-To: <CAHC9VhTwZD7OU9v36HOd28a6jULLJeoQTdNSBYZWSrsY+jf7ZA@mail.gmail.com>

On Thu, Mar 28, 2024 at 08:26:11PM -0400, Paul Moore wrote:

> On Thu, Mar 28, 2024 at 11:38???AM Dr. Greg <greg@enjellic.com> wrote:
> >
> > BPF provides an implementation and would be affected ...

> Casey pretty much summed up my thoughts fairly well, including the
> "Bear poking trimmed" comment, which was worth a good laugh :)

Very good, we will take Casey's e-mail as the official position of the
Linux security maintainers on the functionality under discussion and
similar issues moving forward.

> paul-moore.com

Have a good weekend.

As always,
Dr. Greg

   The Quixote Project - Flailing at the Travails of Cybersecurity
		  https://github.com/Quixote-Project

  reply	other threads:[~2024-03-30 14:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-24 22:32 [PATCH] Do not require attributes for security_inode_init_security Greg Wettstein
2024-03-25 21:08 ` Paul Moore
2024-03-26 10:30   ` Dr. Greg
2024-03-26 19:12     ` Paul Moore
2024-03-27  9:16       ` Dr. Greg
2024-03-27 15:18         ` Paul Moore
2024-03-28 15:38           ` Dr. Greg
2024-03-28 16:34             ` Casey Schaufler
2024-03-30 20:14               ` Dr. Greg
2024-03-31 15:02                 ` Paul Moore
2024-03-29  0:26             ` Paul Moore
2024-03-30 14:46               ` Dr. Greg [this message]
2024-03-30 21:39                 ` 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=20240330144604.GA4625@wind.enjellic.com \
    --to=greg@enjellic.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=roberto.sassu@huaweicloud.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.