From: Casey Schaufler <casey@schaufler-ca.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LSM List <linux-security-module@vger.kernel.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Konstantin Andreev <andreev@swemel.ru>,
Taimoor Zaeem <taimoorzaeem@gmail.com>,
Casey Schaufler <casey@schaufler-ca.com>
Subject: [GIT PULL] Smack patches for 7.0
Date: Mon, 9 Feb 2026 13:15:00 -0800 [thread overview]
Message-ID: <28dea16f-18c3-4a2f-821c-e85b660125ed@schaufler-ca.com> (raw)
In-Reply-To: 28dea16f-18c3-4a2f-821c-e85b660125ed.ref@schaufler-ca.com
Hello Linus,
Here is the Smack pull request for v7.0.
There's nothing exciting. Two improvements to the code for setting
the CIPSO Domain Of Interpretation (DOI), a seldom used feature,
and a formatting change. All tested and included in next for some time.
The following changes since commit f8f9c1f4d0c7a64600e2ca312dec824a0bc2f1da:
Linux 6.19-rc3 (2025-12-28 13:24:26 -0800)
are available in the Git repository at:
https://github.com/cschaufler/smack-next tags/Smack-for-7.0
for you to fetch changes up to 33d589ed60ae433b483761987b85e0d24e54584e:
smack: /smack/doi: accept previously used values (2025-12-30 12:17:15 -0800)
----------------------------------------------------------------
Smack fixes for DOI specification.
----------------------------------------------------------------
Konstantin Andreev (2):
smack: /smack/doi must be > 0
smack: /smack/doi: accept previously used values
Taimoor Zaeem (1):
security: smack: fix indentation in smack_access.c
security/smack/smack_access.c | 2 +-
security/smack/smackfs.c | 79 +++++++++++++++++++++++++++----------------
2 files changed, 51 insertions(+), 30 deletions(-)
next parent reply other threads:[~2026-02-09 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <28dea16f-18c3-4a2f-821c-e85b660125ed.ref@schaufler-ca.com>
2026-02-09 21:15 ` Casey Schaufler [this message]
2026-02-12 0:04 ` [GIT PULL] Smack patches for 7.0 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=28dea16f-18c3-4a2f-821c-e85b660125ed@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=andreev@swemel.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=taimoorzaeem@gmail.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