Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

On 7/20/2016 1:13 PM, Paul Moore wrote: > On Tue, Jul 19, 2016 at 7:37 PM, Casey Schaufler > wrote: >> Digging into this further I have determined that the >> circumstances leading to this issue are somewhat complex. >> The good news is that there seems to be a very

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

On Tue, Jul 19, 2016 at 7:37 PM, Casey Schaufler wrote: > Digging into this further I have determined that the > circumstances leading to this issue are somewhat complex. > The good news is that there seems to be a very limited > circumstances under which the problem

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

On 7/6/2016 11:56 AM, Casey Schaufler wrote: > On 7/6/2016 11:43 AM, David Ahern wrote: >> On 7/6/16 11:01 AM, Casey Schaufler wrote: >>> I find the test occasionally passes without hanging, but will >>> hang the system if repeated. I am running on Ubuntu and Fedora, >>> both with systemd, which

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

On 7/6/2016 11:43 AM, David Ahern wrote: > On 7/6/16 11:01 AM, Casey Schaufler wrote: >> I find the test occasionally passes without hanging, but will >> hang the system if repeated. I am running on Ubuntu and Fedora, >> both with systemd, which may be a contributing factor. I run >> under qemu,

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

On 7/6/16 11:01 AM, Casey Schaufler wrote: I find the test occasionally passes without hanging, but will hang the system if repeated. I am running on Ubuntu and Fedora, both with systemd, which may be a contributing factor. I run under qemu, and am based on Linus' tree. With this: for n in

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

On 7/6/2016 10:40 AM, David Ahern wrote: > On 7/6/16 10:24 AM, Casey Schaufler wrote: >> On 7/6/2016 9:28 AM, David Ahern wrote: >>> 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

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

On 7/6/16 10:24 AM, Casey Schaufler wrote: On 7/6/2016 9:28 AM, David Ahern wrote: 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

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

On 7/6/2016 9:28 AM, David Ahern wrote: > 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

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

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

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

On 7/6/2016 7:03 AM, Paul Moore wrote: > On Wed, Jul 6, 2016 at 8:50 AM, Paul Moore wrote: >> On Tue, Jul 5, 2016 at 8:38 PM, Casey Schaufler >> wrote: >>> I have encountered a system hang with my Smack >>> networking tests that bisects to the change

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

On Wed, Jul 6, 2016 at 10:15 AM, Casey Schaufler wrote: > On 7/6/2016 5:50 AM, Paul Moore wrote: >> On Tue, Jul 5, 2016 at 8:38 PM, Casey Schaufler >> wrote: >>> I have encountered a system hang with my Smack >>> networking tests that bisects to

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

On 7/6/2016 5:50 AM, Paul Moore wrote: > On Tue, Jul 5, 2016 at 8: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

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

On Wed, Jul 6, 2016 at 8:50 AM, Paul Moore wrote: > On Tue, Jul 5, 2016 at 8: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

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

On Tue, Jul 5, 2016 at 8: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

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

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 >>

Re: Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

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

Network hang after c3f1010b30f7fc611139cfb702a8685741aa6827 with CIPSO & Smack

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