linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roberto Sassu <roberto.sassu@huaweicloud.com>
To: torvalds@linux-foundation.org
Cc: linux-integrity@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-cifs@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Roberto Sassu <roberto.sassu@huawei.com>
Subject: [GIT PULL] security changes for v6.9-rc3
Date: Tue,  2 Apr 2024 11:21:08 +0200	[thread overview]
Message-ID: <20240402092108.2520373-1-roberto.sassu@huaweicloud.com> (raw)

From: Roberto Sassu <roberto.sassu@huawei.com>

Hi Linus

I have a small bug fix for this kernel version. Please pull.

PS: sorry for the email mismatch, @huawei.com emails resent from the
    mailing list are classified by Gmail as spam, we are working on
    fixing it.

Thanks

Roberto


The following changes since commit 026e680b0a08a62b1d948e5a8ca78700bfac0e6e:

  Merge tag 'pwm/for-6.9-rc3-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux (2024-04-01 14:38:55 -0700)

are available in the Git repository at:

  https://github.com/linux-integrity/linux.git tags/security-mknod-6.9-rc3

for you to fetch changes up to 12d665b7d3fa743ec58160ceda8421d64b63f272:

  security: Handle dentries without inode in security_path_post_mknod() (2024-04-02 10:01:19 +0200)

----------------------------------------------------------------
Here is a simple follow-up patch for the patch set to move IMA and EVM to
the LSM infrastructure.

It fixes a kernel panic in the newly introduced function
security_path_post_mknod(), when trying to check if an inode is private.
The panic occurs because not all dentries have an inode attached to them.

I'm sending this PR as IMA/EVM co-maintainer, even if the patch also
touches the LSM infrastructure itself (it is acked by Paul).

Signed-off-by: Roberto Sassu <roberto.sassu@huawei.com>

----------------------------------------------------------------
Roberto Sassu (1):
      security: Handle dentries without inode in security_path_post_mknod()

 security/integrity/evm/evm_main.c | 6 ++++--
 security/integrity/ima/ima_main.c | 5 +++--
 security/security.c               | 5 ++++-
 3 files changed, 11 insertions(+), 5 deletions(-)


             reply	other threads:[~2024-04-02  9:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02  9:21 Roberto Sassu [this message]
2024-04-02 12:15 ` [GIT PULL] security changes for v6.9-rc3 Roberto Sassu
2024-04-02 14:11 Roberto Sassu
2024-04-02 19:39 ` Linus Torvalds
2024-04-02 19:57   ` Linus Torvalds
2024-04-02 21:00     ` Al Viro
2024-04-02 21:35       ` Linus Torvalds
2024-04-02 21:36       ` Paul Moore
2024-04-02 22:42         ` Al Viro
2024-04-03  2:21           ` Paul Moore
2024-04-09 17:37         ` Eric W. Biederman
2024-04-09 20:14           ` Paul Moore
2024-04-02 20:27   ` Paul Moore
2024-04-02 20:28     ` 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=20240402092108.2520373-1-roberto.sassu@huaweicloud.com \
    --to=roberto.sassu@huaweicloud.com \
    --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=roberto.sassu@huawei.com \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).