Re: reproducible kernel crash in NetBSD 7.1_RC1

2017-01-24 Thread Christos Zoulas 
In article <pine.neb.4.64.1701240956200.22...@6bone.informatik.uni-leipzig.de>,
 <6b...@6bone.informatik.uni-leipzig.de> wrote:
>On Mon, 23 Jan 2017, Christos Zoulas wrote:
>
>> Date: Mon, 23 Jan 2017 19:35:06 + (UTC)
>> From: Christos Zoulas <chris...@astron.com>
>> To: current-users@netbsd.org
>> Subject: Re: reproducible kernel crash in NetBSD 7.1_RC1
>> 
>> I think that the vlan creation/removal code is racy even under /current.
>> There was some discussion recently about it.
>>
>I have unfortunately not heard the discussion. Is it planned to solve the 
>problem in the near future?

I asked to try a patch protecting vlan creation and removal with a mutex.

christos

Re: reproducible kernel crash in NetBSD 7.1_RC1

2017-01-24 Thread 6bone 

On Mon, 23 Jan 2017, Christos Zoulas wrote:


Date: Mon, 23 Jan 2017 19:35:06 + (UTC)
From: Christos Zoulas <chris...@astron.com>
To: current-users@netbsd.org
Subject: Re: reproducible kernel crash in NetBSD 7.1_RC1

I think that the vlan creation/removal code is racy even under /current.
There was some discussion recently about it.

I have unfortunately not heard the discussion. Is it planned to solve the 
problem in the near future?

christos


Regards
Uwe

Re: reproducible kernel crash in NetBSD 7.1_RC1

2017-01-23 Thread Christos Zoulas 
In article ,
 <6b...@6bone.informatik.uni-leipzig.de> wrote:
>Hello,
>
>on NetBSD 7.1_RC1 (and earlier) I can create a kernel crash as follows:
>
>ifconfig ixg0 ip4csum tcp4csum udp4csum tcp6csum udp6csum ip4csum-tx
>ip4csum-rx tcp4csum-tx tcp4csum-rx udp4csum-tx udp4csum-rx tcp6csum-tx
>tcp6csum-rx udp6csum-tx udp6csum-rx tso4 tso6
>ifconfig vlan850 create
>ifconfig vlan850 vlan 850 vlanif ixg0 up
>ifconfig vlan850 ip4csum tcp4csum udp4csum tcp6csum udp6csum ip4csum-tx
>ip4csum-rx tcp4csum-tx tcp4csum-rx udp4csum-tx udp4csum-rx tcp6csum-tx
>tcp6csum-rx udp6csum-tx udp6csum-rx tso4 tso6
>ifconfig vlan850 destroy
>
>If it does not work, try again.
>
>Can anyone take a look at the problem or should I make a bug report?
>
>Thank you for your efforts

I think that the vlan creation/removal code is racy even under /current.
There was some discussion recently about it.

christos