mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mickaël Salaün" <mic@digikod.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Mickaël Salaün" <mic@digikod.net>,
	"Günther Noack" <gnoack@google.com>,
	"Paul Moore" <paul@paul-moore.com>,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: [GIT PULL] Landlock fix for v6.10-rc2
Date: Fri, 31 May 2024 17:40:34 +0200	[thread overview]
Message-ID: <20240531154034.198316-1-mic@digikod.net> (raw)

Hi Linus,

This PR fixes a wrong path walk triggered by syzkaller.

Please pull these changes for v6.10-rc2.  This commit merged cleanly with your
master branch.  The kernel code has been tested in the latest linux-next
releases for two weeks, but I rebased it on v6.10-rc1 to fix a commit message
and properly test it again.

Regards,
 Mickaël

--
The following changes since commit 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0:

  Linux 6.10-rc1 (2024-05-26 15:20:12 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git tags/landlock-6.10-rc2

for you to fetch changes up to 0055f53aac80fd938bf7cdfad7ad414ca6c0e198:

  selftests/landlock: Add layout1.refer_mount_root (2024-05-31 16:41:54 +0200)

----------------------------------------------------------------
Landlock fix for v6.10-rc2

----------------------------------------------------------------
Mickaël Salaün (2):
      landlock: Fix d_parent walk
      selftests/landlock: Add layout1.refer_mount_root

 security/landlock/fs.c                     | 13 +++++++--
 tools/testing/selftests/landlock/fs_test.c | 45 ++++++++++++++++++++++++++++++
 2 files changed, 56 insertions(+), 2 deletions(-)

             reply	other threads:[~2024-05-31 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31 15:40 Mickaël Salaün [this message]
2024-06-01 16:38 ` pr-tracker-bot

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=20240531154034.198316-1-mic@digikod.net \
    --to=mic@digikod.net \
    --cc=gnoack@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.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

all inboxes | Powered by JetHome®