All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Greg KH <gregkh@linuxfoundation.org>, GUO Zihua <guozihua@huawei.com>
Cc: stable@vger.kernel.org, paul@paul-moore.com,
	linux-integrity@vger.kernel.org, luhuaxin1@huawei.com
Subject: Re: [PATCH 2/2] ima: Handle -ESTALE returned by ima_filter_rule_match()
Date: Tue, 27 Dec 2022 06:56:15 -0500	[thread overview]
Message-ID: <d65e2d46bf41e3d58c0fa18bd274faf20dadb523.camel@linux.ibm.com> (raw)
In-Reply-To: <Y6qgqO/LJ/wHUk5x@kroah.com>

On Tue, 2022-12-27 at 08:37 +0100, Greg KH wrote:
> On Tue, Dec 27, 2022 at 09:47:29AM +0800, GUO Zihua wrote:
> > [ Upstream commit c7423dbdbc9ecef7fff5239d144cad4b9887f4de ]
> 
> For obvious reasons we can not only take this patch (from 6.2-rc1) into
> 4.19.y as that would cause people who upgrade from 4.19.y to a newer
> stable kernel to have a regression.
> 
> Please submit backports for all stable kernels if you wish to see this
> in older ones to prevent problems like this from happening.

Sasha has already queued the original commit and the dependencies for
the 6.1, 6.0, and 5.15 stable kernels.  Those kernels all had the
call_lsm_notifier() to call_blocking_lsm_notifier() change.  Prior to
5.3, the change to the blocking notifier would need to be backported as
well.  This version of the backport still needs to be reviewed.

thanks,

Mimi

> 
> But also, why are you still on 4.19.y?  What is wrong with 5.4.y at this
> point in time?  If we dropped support for 4.19.y in January, what would
> that cause to happen for your systems?
> 
> thanks,
> 
> greg k-h
> 


  reply	other threads:[~2022-12-27 11:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-27  1:47 [PATCH 0/2] ima: Fix IMA mishandling of LSM based rule during GUO Zihua
2022-12-27  1:47 ` [PATCH 1/2] ima: use the lsm policy update notifier GUO Zihua
2022-12-27  1:47 ` [PATCH 2/2] ima: Handle -ESTALE returned by ima_filter_rule_match() GUO Zihua
2022-12-27  7:37   ` Greg KH
2022-12-27 11:56     ` Mimi Zohar [this message]
2022-12-30  6:18       ` Guozihua (Scott)

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=d65e2d46bf41e3d58c0fa18bd274faf20dadb523.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=guozihua@huawei.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=luhuaxin1@huawei.com \
    --cc=paul@paul-moore.com \
    --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 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.