mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: torvalds@linux-foundation.org
Cc: linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, casey@schaufler-ca.com
Subject: [GIT PULL] Smack patches for v5.18
Date: Mon, 21 Mar 2022 09:34:59 -0700	[thread overview]
Message-ID: <bf678bae-821c-02ab-042a-004c03d9c334@schaufler-ca.com> (raw)
In-Reply-To: <bf678bae-821c-02ab-042a-004c03d9c334.ref@schaufler-ca.com>

Hello Linus,

Here is the Smack pull request for v5.18.

There is a single change to repair an incorrect use of
ntohs() in IPv6 audit code. It's very minor and went unnoticed
until lkp found it. It's been in next and passes all tests.
Thank you.

The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:

  Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)

are available in the Git repository at:

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

for you to fetch changes up to a5cd1ab7ab679d252a6d2f483eee7d45ebf2040c:

  Fix incorrect type in assignment of ipv6 port for audit (2022-02-28 15:45:32 -0800)

----------------------------------------------------------------
Smack updates for 5.18
    Fix incorrect type in assignment of ipv6 port for audit

----------------------------------------------------------------
Casey Schaufler (1):
      Fix incorrect type in assignment of ipv6 port for audit

 security/smack/smack_lsm.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


       reply	other threads:[~2022-03-21 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bf678bae-821c-02ab-042a-004c03d9c334.ref@schaufler-ca.com>
2022-03-21 16:34 ` Casey Schaufler [this message]
2022-03-22  3:56   ` 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=bf678bae-821c-02ab-042a-004c03d9c334@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --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®