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>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Günther Noack" <gnoack@google.com>,
	"Tingmao Wang" <m@maowtm.org>,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org
Subject: [GIT PULL] Landlock fix for v7.3-rc5
Date: Thu, 24 Sep 2026 18:19:52 +0200	[thread overview]
Message-ID: <20260924161952.1104402-1-mic@digikod.net> (raw)

Hi,

This mainly fixes the Landlock tracepoint support merged this cycle so
that denial and rule events report the intended policy context, whether
through tracefs or BTF-visible callbacks.  The size comes from
propagating the corrected contract through event definitions and
producers, adding new tests for the reported context, and updating the
documentation.  This PR also improves annotation and fixes a GCC 16
build warning.

Please pull these changes for v7.3-rc5 .  These commits have been part
of latest linux-next releases and merge cleanly with your master branch.

Test coverage for security/landlock is 91.6% of 2625 lines according to
LLVM 22, and it was 91.6% of 2574 lines before this PR.

Regards,
 Mickaël

--
The following changes since commit fd73f4a6659897191fa0d40695fe370925dd3780:

  Linux 7.3-rc3 (2026-09-13 14:38:02 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/mic/linux.git tags/landlock-7.3-rc5

for you to fetch changes up to e7e0a54300a896e731dffd3e2e8dae5631d6243d:

  landlock: Widen ruleset versions to 64 bits (2026-09-22 20:52:13 +0200)

----------------------------------------------------------------
Landlock fix for v7.3-rc5

----------------------------------------------------------------
Arnd Bergmann (1):
      landlock: Work around gcc-16 -Wuninitialized warning

Mickaël Salaün (10):
      landlock: Fix tracepoint fixed-width type names
      landlock: Fix filesystem denial blocker reporting
      landlock: Fix rule tracepoint context
      landlock: Fix network denial trace context
      landlock: Report the actual ptrace tracer
      landlock: Report the effective signal number
      selftests/landlock: Test filesystem denial blockers
      selftests/landlock: Test network denial context
      landlock: Fix tracepoint contract documentation
      landlock: Widen ruleset versions to 64 bits

Tingmao Wang (1):
      landlock: Add counted_by in landlock_domain

 Documentation/trace/events-landlock.rst          |  52 ++--
 include/trace/events/landlock.h                  | 301 ++++++++++++++---------
 security/landlock/access.h                       |   8 +
 security/landlock/domain.h                       |   3 +-
 security/landlock/fs.c                           |  10 +-
 security/landlock/log.h                          |  52 +++-
 security/landlock/net.c                          |  42 +++-
 security/landlock/ruleset.h                      |   5 +-
 security/landlock/task.c                         |  87 ++++---
 security/landlock/trace.c                        |  71 ++++--
 tools/testing/selftests/landlock/fs_test.c       |  28 +--
 tools/testing/selftests/landlock/net_test.c      | 295 +++++++++++-----------
 tools/testing/selftests/landlock/trace.h         |  59 +++--
 tools/testing/selftests/landlock/trace_fs_test.c | 130 ++++++++--
 tools/testing/selftests/landlock/trace_test.c    |  51 ++--
 15 files changed, 753 insertions(+), 441 deletions(-)

             reply	other threads:[~2026-09-24 16:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 16:19 Mickaël Salaün [this message]
2026-09-24 17:59 ` 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=20260924161952.1104402-1-mic@digikod.net \
    --to=mic@digikod.net \
    --cc=arnd@arndb.de \
    --cc=gnoack@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=m@maowtm.org \
    --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®