All of lore.kernel.org
 help / color / mirror / Atom feed
From: Munehisa Kamata <kamatam@amazon.com>
To: <sashal@kernel.org>
Cc: <casey@schaufler-ca.com>, <kamatam@amazon.com>,
	<roberto.sassu@huawei.com>, <stable@vger.kernel.org>,
	<vishal.goel@samsung.com>
Subject: Re: [PATCH for 4.19.y 0/3] Backport Smack fixes for 4.19.y
Date: Tue, 3 Oct 2023 12:02:17 -0700	[thread overview]
Message-ID: <20231003190217.35669-1-kamatam@amazon.com> (raw)
In-Reply-To: <ZRv6gaFF0hPrhj+D@sashalap>

Hi Sasha,

On Tue, 2023-10-03 11:26:57 +0000, Sasha Levin wrote:
>
> On Thu, Sep 28, 2023 at 06:51:35PM -0700, Munehisa Kamata wrote:
> >This series backports the following fixes for Smack problems with overlayfs
> >to 4.19.y.
> >
> >2c085f3a8f23 smack: Record transmuting in smk_transmuted
> >3a3d8fce31a4 smack: Retrieve transmuting information in smack_inode_getsecurity()
> >387ef964460f Smack:- Use overlay inode label in smack_inode_copy_up()
> >
> >This slightly modifies the original commits, because the commits rely on
> >some helper functions introduced after v4.19 by different commits that
> >touch more code than just Smack, require even more prerequisite commits and
> >also need some adjustments for 4.19.y.  Instead, this series makes minor
> >modifications for only the overlayfs-related fixes to not use the helper
> >functions rather than backporting everything.
> 
> What about newer trees? We can't take fixes for 4.19 if the fixes don't
> exist in 5.4+.

Sorry if it was not clear enough in the first post[1]. For 5.4+, please just
cherry-pick the 3 commits. Those should apply cleanly.

[1] https://lore.kernel.org/stable/20230929015033.835263-1-kamatam@amazon.com/

Thanks,
Munehisa
 
> -- 
> Thanks,
> Sasha
> 

  reply	other threads:[~2023-10-03 19:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29  1:50 Request to cherry-pick a few Smack fixes Munehisa Kamata
2023-09-29  1:51 ` [PATCH for 4.19.y 0/3] Backport Smack fixes for 4.19.y Munehisa Kamata
2023-09-29  1:51   ` [PATCH for 4.19.y 1/3] Smack:- Use overlay inode label in smack_inode_copy_up() Munehisa Kamata
2023-09-29  1:51   ` [PATCH for 4.19.y 2/3] smack: Retrieve transmuting information in smack_inode_getsecurity() Munehisa Kamata
2023-09-29  1:51   ` [PATCH for 4.19.y 3/3] smack: Record transmuting in smk_transmuted Munehisa Kamata
2023-10-03 11:26   ` [PATCH for 4.19.y 0/3] Backport Smack fixes for 4.19.y Sasha Levin
2023-10-03 19:02     ` Munehisa Kamata [this message]
2023-10-04 10:00       ` Sasha Levin

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=20231003190217.35669-1-kamatam@amazon.com \
    --to=kamatam@amazon.com \
    --cc=casey@schaufler-ca.com \
    --cc=roberto.sassu@huawei.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vishal.goel@samsung.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.