On Fri, May 2, 2014 at 3:08 PM, Alexander V. Chernikov
wrote:
> On 03.05.2014 00:22, Alan Somers wrote:
>> On Fri, May 2, 2014 at 11:01 AM, Alexander V. Chernikov
>> wrote:
>>> On 02.05.2014 20:24, Alan Somers wrote:
Author: asomers
Date: Fri May 2 16:24:09 2014
New Revision:
On 03.05.2014 00:22, Alan Somers wrote:
> On Fri, May 2, 2014 at 11:01 AM, Alexander V. Chernikov
> wrote:
>> On 02.05.2014 20:24, Alan Somers wrote:
>>>
>>> Author: asomers
>>> Date: Fri May 2 16:24:09 2014
>>> New Revision: 265232
>>> URL: http://svnweb.freebsd.org/changeset/base/265232
>>>
>>>
On Fri, May 2, 2014 at 11:01 AM, Alexander V. Chernikov
wrote:
> On 02.05.2014 20:24, Alan Somers wrote:
>>
>> Author: asomers
>> Date: Fri May 2 16:24:09 2014
>> New Revision: 265232
>> URL: http://svnweb.freebsd.org/changeset/base/265232
>>
>> Log:
>>Fix a panic caused by doing "ifconfig -a
On 02.05.2014 20:24, Alan Somers wrote:
Author: asomers
Date: Fri May 2 16:24:09 2014
New Revision: 265232
URL: http://svnweb.freebsd.org/changeset/base/265232
Log:
Fix a panic caused by doing "ifconfig -am" while a lagg is being destroyed.
The thread that is destroying the lagg has alrea
Author: asomers
Date: Fri May 2 16:24:09 2014
New Revision: 265232
URL: http://svnweb.freebsd.org/changeset/base/265232
Log:
Fix a panic caused by doing "ifconfig -am" while a lagg is being destroyed.
The thread that is destroying the lagg has already set sc->sc_psc=NULL when
the "ifconfig