linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Linux Security Module list 
	<linux-security-module@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Casey Schaufler <casey@schaufler-ca.com>
Subject: [GIT PULL] Smack patch for v5.6
Date: Wed, 5 Feb 2020 18:07:09 -0800	[thread overview]
Message-ID: <7300e604-6fb5-16b1-4e1b-dfae7b494853@schaufler-ca.com> (raw)
In-Reply-To: 7300e604-6fb5-16b1-4e1b-dfae7b494853.ref@schaufler-ca.com

Apologies for the late pull request. Testing on the originating
configuration was unfortunately delayed.
One fix for an obscure error found using an old version of
ping(1) that did not use IPv6 sockets in the documented way.

The following changes since commit d5226fa6dbae0569ee43ecfc08bdcd6770fc4755:

  Linux 5.5 (2020-01-26 16:23:03 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 87fbfffcc89b92a4281b0aa53bd06af714087889:

  broken ping to ipv6 linklocal addresses on debian buster (2020-02-05 14:16:27 -0800)

----------------------------------------------------------------
Smack change for Linux 5.6

----------------------------------------------------------------
Casey Schaufler (1):
      broken ping to ipv6 linklocal addresses on debian buster

 security/smack/smack_lsm.c | 41 +++++++++++++++++++----------------------
 1 file changed, 19 insertions(+), 22 deletions(-)


       reply	other threads:[~2020-02-06  2:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7300e604-6fb5-16b1-4e1b-dfae7b494853.ref@schaufler-ca.com>
2020-02-06  2:07 ` Casey Schaufler [this message]
2020-02-06  8:20   ` [GIT PULL] Smack patch for v5.6 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=7300e604-6fb5-16b1-4e1b-dfae7b494853@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;
as well as URLs for NNTP newsgroup(s).