mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	Casey Schaufler <casey@schaufler-ca.com>,
	Konstantin Andreev <andreev@swemel.ru>
Subject: [GIT PULL] Smack patches for 6.11
Date: Mon, 15 Jul 2024 16:30:34 -0700	[thread overview]
Message-ID: <c9842562-3564-4977-880f-9042ebe43e62@schaufler-ca.com> (raw)
In-Reply-To: <c9842562-3564-4977-880f-9042ebe43e62.ref@schaufler-ca.com>

Hello Linus,

Here is the Smack pull request for v6.11.

There are 2 patches. Both address network labeling issues.
Both have been in the next branch and pass all tests.

The following changes since commit c3f38fa61af77b49866b006939479069cd451173:

  Linux 6.10-rc2 (2024-06-02 15:44:56 -0700)

are available in the Git repository at:

  https://github.com/cschaufler/smack-next tags/Smack-for-6.10

for you to fetch changes up to e86cac0acdb1a74f608bacefe702f2034133a047:

  smack: unix sockets: fix accept()ed socket label (2024-06-19 09:25:00 -0700)

----------------------------------------------------------------
Two fixes for Smack networking by Konstantin Andreev.

----------------------------------------------------------------
Casey Schaufler (1):
      smack: tcp: ipv4, fix incorrect labeling

Konstantin Andreev (1):
      smack: unix sockets: fix accept()ed socket label

 security/smack/smack_lsm.c | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)


       reply	other threads:[~2024-07-15 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c9842562-3564-4977-880f-9042ebe43e62.ref@schaufler-ca.com>
2024-07-15 23:30 ` Casey Schaufler [this message]
2024-07-16 21: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=c9842562-3564-4977-880f-9042ebe43e62@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=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®