From: David Ahern <dsa@cumulusnetworks.com>
To: Casey Schaufler <casey@schaufler-ca.com>,
David Miller <davem@davemloft.net>,
Paul Moore <paul@paul-moore.com>
Cc: Linux-Netdev <netdev@vger.kernel.org>
Subject: Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack
Date: Tue, 5 Jul 2016 17:49:41 -0700 [thread overview]
Message-ID: <7d833f59-c68f-f779-4de4-15bc0b26ac7c@cumulusnetworks.com> (raw)
In-Reply-To: <e5ba1ba9-acf6-c36c-03e4-4cdc81e81648@schaufler-ca.com>
On 7/5/16 5:38 PM, Casey Schaufler wrote:
> I have encountered a system hang with my Smack
> networking tests that bisects to the change below.
> I can't say that I have any idea why the change
> would impact the Smack processing, but there appears
> to be some serious packet processing going on. The
> Smack code is using CIPSO on the loopback interface.
> The test is supposed to verify that labels can be
> set on the packets using CIPSO. Unlabeled packets
> do not appear to be impacted. I do not know if SELinux
> is affected, and if not, why not. Smack and SELinux
> use CIPSO differently.
What are the commands to repeat the test?
next prev parent reply other threads:[~2016-07-06 0:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 0:38 Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack Casey Schaufler
2016-07-06 0:49 ` David Ahern [this message]
2016-07-06 1:31 ` Casey Schaufler
2016-07-06 16:28 ` David Ahern
2016-07-06 17:24 ` Casey Schaufler
2016-07-06 17:40 ` David Ahern
2016-07-06 18:01 ` Casey Schaufler
2016-07-06 18:43 ` David Ahern
2016-07-06 18:56 ` Casey Schaufler
2016-07-19 23:37 ` Casey Schaufler
2016-07-20 20:13 ` Paul Moore
2016-07-21 22:55 ` Casey Schaufler
2016-07-06 12:50 ` Paul Moore
2016-07-06 14:03 ` Paul Moore
2016-07-06 14:42 ` Casey Schaufler
2016-07-06 14:15 ` Casey Schaufler
2016-07-06 14:37 ` Paul Moore
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=7d833f59-c68f-f779-4de4-15bc0b26ac7c@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=casey@schaufler-ca.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
/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