From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Ahern Subject: Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack Date: Wed, 6 Jul 2016 09:28:57 -0700 Message-ID: <9998a0da-b273-43d4-84ad-a0539e6a69ac@cumulusnetworks.com> References: <7d833f59-c68f-f779-4de4-15bc0b26ac7c@cumulusnetworks.com> <66709b13-15a7-8d03-9e84-e4be9aab60b5@schaufler-ca.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Linux-Netdev To: Casey Schaufler , David Miller , Paul Moore Return-path: Received: from mail-pf0-f182.google.com ([209.85.192.182]:33897 "EHLO mail-pf0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754469AbcGFQ27 (ORCPT ); Wed, 6 Jul 2016 12:28:59 -0400 Received: by mail-pf0-f182.google.com with SMTP id h14so81042997pfe.1 for ; Wed, 06 Jul 2016 09:28:59 -0700 (PDT) In-Reply-To: <66709b13-15a7-8d03-9e84-e4be9aab60b5@schaufler-ca.com> Sender: netdev-owner@vger.kernel.org List-ID: On 7/5/16 6:31 PM, Casey Schaufler wrote: > On 7/5/2016 5:49 PM, David Ahern wrote: >> 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? >> > There is a tar file attached with the tests. > Put the etc/smack/user file into /etc/smack/user. > In the tools-2012 directory run make to build > the tools. The test in question is called > testnetworking.sh and needs to be run as root. > You will need to configure Smack in the kernel, > of course. > I understand Paul's point and glad to see the changes are not causing issues with his SELinux testing. I have tried to reproduce the lockup you are seeing but not successful. I am using a jessie based VM with latest net-next kernel. root@kenny-jessie3:~/smack/tools-2012# zcat /proc/config.gz | grep SMACK CONFIG_SECURITY_SMACK=y CONFIG_SECURITY_SMACK_BRINGUP=y CONFIG_SECURITY_SMACK_NETFILTER=y # CONFIG_DEFAULT_SECURITY_SMACK is not set root@kenny-jessie3:~/smack/tools-2012# bash -x ./testnetworking.sh Send me your kernel config. Perhaps I do not have some config enabled.