public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Paul Moore <paul@paul-moore.com>
Cc: Luiz Capitulino <luizcap@amazon.com>,
	sashal@kernel.org, stable@vger.kernel.org
Subject: Re: Possible build time regression affecting stable kernels
Date: Thu, 29 Jun 2023 10:43:31 +0200	[thread overview]
Message-ID: <2023062955-wing-front-553b@gregkh> (raw)
In-Reply-To: <CAHC9VhQfWNxP80PRHMM44fkMx8fnuPJ2VyR-mA1WMLwsAevRuA@mail.gmail.com>

On Wed, Jun 28, 2023 at 07:33:27PM -0400, Paul Moore wrote:
> > So, can I get a directory list or file list of what we should be
> > ignoring for the AUTOSEL and "Fixes: only" tools to be ignoring?
> 
> I've been trying to ensure that the files/directories entries in
> MAINTAINERS are current, so that is probably as good a place as any to
> pull that info.  Do the stable tools use that info already?  In other
> words, if we update the entries in MAINTAINERS should we also notify
> you guys, or will you get it automatically?

We do not use (or at least I don't, I can't speak for Sasha here, but
odds are we should unify this now), the MAINTAINERS file for this, but
rather a list like you provided below, thanks.

> Regardless, here is a list:
> 
> * Audit
> include/asm-generic/audit_*.h
> include/linux/audit.h
> include/linux/audit_arch.h
> include/uapi/linux/audit.h
> kernel/audit*
> lib/*audit.c
> 
> * LSM layer
> security/
> (NOTE: the individual sub-dirs under security/ belong to the
> individual LSMs, not the LSM layer)

So security/*.c would cover this, not below that, right?

> * SELinux
> include/trace/events/avc.h
> include/uapi/linux/selinux_netlink.h
> scripts/selinux/
> security/selinux/

Looks good, thanks for this.

greg k-h

  reply	other threads:[~2023-06-29  8:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01  2:12 Possible build time regression affecting stable kernels Luiz Capitulino
2023-06-01  6:06 ` Greg KH
2023-06-01 13:13   ` Luiz Capitulino
2023-06-01 13:20     ` Greg KH
2023-06-01 13:26       ` Luiz Capitulino
2023-06-01 14:13         ` Greg KH
2023-06-01 14:22           ` Luiz Capitulino
2023-06-01 14:56       ` Paul Moore
2023-06-01 15:51         ` Greg KH
2023-06-01 18:39           ` Paul Moore
2023-06-28 18:33             ` Greg KH
2023-06-28 23:33               ` Paul Moore
2023-06-29  8:43                 ` Greg KH [this message]
2023-06-29 15:55                   ` Paul Moore
2023-06-29 16:07                     ` Greg KH
2023-06-29 16:20                       ` Paul Moore
2023-06-01 14:27 ` Paul Moore
2023-06-01 15:02   ` Luiz Capitulino
2023-06-01 15:45     ` Paul Moore
2023-06-01 15:50       ` Luiz Capitulino
2023-06-01 17:05         ` Greg KH
2023-06-01 18:10           ` Paul Moore
2023-06-01 18:15             ` Luiz Capitulino
2023-06-01 18:41               ` 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=2023062955-wing-front-553b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=luizcap@amazon.com \
    --cc=paul@paul-moore.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.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