From: Mimi Zohar <zohar@linux.ibm.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Roberto Sassu <roberto.sassu@huaweicloud.com>,
dmitry.kasatkin@gmail.com, eric.snowberg@oracle.com,
jmorris@namei.org, serge@hallyn.com,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-cifs@vger.kernel.org, viro@zeniv.linux.org.uk,
pc@manguebit.com, christian@brauner.io,
Roberto Sassu <roberto.sassu@huawei.com>,
stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
Greg KH <greg@kroah.com>
Subject: Re: [PATCH 2/2] ima: evm: Rename *_post_path_mknod() to *_path_post_mknod()
Date: Fri, 29 Mar 2024 15:27:58 -0400 [thread overview]
Message-ID: <1fe6813db395563be658a9b557931cf4db949100.camel@linux.ibm.com> (raw)
In-Reply-To: <CAHC9VhS49p-rffsP4gW5C-C6kOqFfBWJhLrfB_zunp7adXe2cQ@mail.gmail.com>
[Cc: Sasha, Greg]
On Fri, 2024-03-29 at 15:12 -0400, Paul Moore wrote:
> I'd take it one step further and remove both 'Fixes' tags. A 'Fixes'
> tag implies a flaw in the functionality of the code, this is just a
> function rename.
Totally agree.
> Another important thing to keep in mind about 'Fixes' tags, unless
> you've told the stable kernel folks to only take patches that you've
> explicitly marked for stable, they are likely going to attempt to
> backport anything with a 'Fixes' tag.
How do we go about doing that? Do we just send an email to stable?
Is it disabled for security? I thought new functionality won't be backported.
Hopefully the changes for making IMA & EVM full fledged LSMs won't be
automatically backported to stable.
thanks,
Mimi
next prev parent reply other threads:[~2024-03-29 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 10:56 [PATCH 1/2] security: Handle dentries without inode in security_path_post_mknod() Roberto Sassu
2024-03-29 10:56 ` [PATCH 2/2] ima: evm: Rename *_post_path_mknod() to *_path_post_mknod() Roberto Sassu
2024-03-29 15:16 ` Mimi Zohar
2024-03-29 15:45 ` Roberto Sassu
2024-03-29 19:12 ` Paul Moore
2024-03-29 19:27 ` Mimi Zohar [this message]
2024-03-29 19:56 ` Paul Moore
2024-03-29 15:05 ` [PATCH 1/2] security: Handle dentries without inode in security_path_post_mknod() Mimi Zohar
2024-03-29 15:42 ` Roberto Sassu
2024-03-29 19:06 ` 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=1fe6813db395563be658a9b557931cf4db949100.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=christian@brauner.io \
--cc=dmitry.kasatkin@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=greg@kroah.com \
--cc=jmorris@namei.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=pc@manguebit.com \
--cc=roberto.sassu@huawei.com \
--cc=roberto.sassu@huaweicloud.com \
--cc=sashal@kernel.org \
--cc=serge@hallyn.com \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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