public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Robert Kolchmeyer <rkolchmeyer@google.com>
Cc: Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org, linux-integrity@vger.kernel.org,
	regressions@lists.linux.dev, eric.snowberg@oracle.com,
	zohar@linux.ibm.com, jlayton@kernel.org
Subject: Re: IMA performance regression in 5.10.194 when using overlayfs
Date: Mon, 18 Dec 2023 12:58:46 +0100	[thread overview]
Message-ID: <2023121834-abiding-armory-e468@gregkh> (raw)
In-Reply-To: <2023121848-filter-pacifier-c457@gregkh>

On Mon, Dec 18, 2023 at 12:57:20PM +0100, Greg KH wrote:
> On Tue, Dec 12, 2023 at 04:37:31PM -0800, Robert Kolchmeyer wrote:
> > > Looking at the dependencies you've identified, it probably makes sense
> > > to just take them as is (as it's something we would have done if these
> > > dependencies were identified explicitly).
> > >
> > > I'll plan to queue them up after the current round of releases is out.
> > 
> > Sounds great, thank you!
> 
> I've dropped them now as there are some reported bug fixes with just
> that commit that do not seem to apply properly at all, and we can't add
> new problems when we know we are doing so :)
> 
> So can you provide a working set of full backports for the relevant
> kernels that include all fixes (specifically stuff like 8a924db2d7b5
> ("fs: Pass AT_GETATTR_NOSEC flag to getattr interface function")) so
> that we can properly queue them up then?

Also don't forget 18b44bc5a672 ("ovl: Always reevaluate the file
signature for IMA") either.  There might be more...

thanks,

greg k-h

  reply	other threads:[~2023-12-18 11:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12  0:40 IMA performance regression in 5.10.194 when using overlayfs rkolchmeyer
2023-12-12  2:12 ` Sasha Levin
2023-12-13  0:37   ` Robert Kolchmeyer
2023-12-18 11:57     ` Greg KH
2023-12-18 11:58       ` Greg KH [this message]
2023-12-18 19:39         ` Robert Kolchmeyer

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=2023121834-abiding-armory-e468@gregkh \
    --to=greg@kroah.com \
    --cc=eric.snowberg@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=rkolchmeyer@google.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=zohar@linux.ibm.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