[Bug 206219] Kernel panic from lagg_ioctl and lagg_port_ioctl

2017-09-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206219 Kevin Bowling changed: What|Removed |Added CC||kbowl...@freebsd.org Resol

[Bug 206219] Kernel panic from lagg_ioctl and lagg_port_ioctl

2016-01-14 Thread bugzilla-noreply
from lagg_ioctl and lagg_port_ioctl r287723 removed some cleanup from lagg(4), which leads to panics when changing configuration. Restore the spirit of the code which was removed. This issue has been refactored out of existence in -HEAD, so this patch is directly against stable/10. PR

[Bug 206219] Kernel panic from lagg_ioctl and lagg_port_ioctl

2016-01-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206219 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org K

Re: Kernel panic from lagg_ioctl and lagg_port_ioctl

2016-01-13 Thread Lewis, Fred
Hi Hans, Can you give an example of draining the callouts? Thanks, -Fred On 1/13/16 7:33 AM, "Lakshmi Narasimhan Sundararajan" mailto:lakshm...@msystechnologies.com>> wrote: Hi Hans, Yes, we understand that piece of code. But Panasas wants this change to MFC to 10.3. This issue is not seen in

Re: Kernel panic from lagg_ioctl and lagg_port_ioctl

2016-01-13 Thread Hans Petter Selasky
On 01/13/16 14:15, Lewis, Fred wrote: Hi Hans, Can you give an example of draining the callouts? Hi, man 9 callout_drain and man 9 callout_async_drain (11-current) callout_drain() might sleep and needs a context which allows for that. Else use callout_async_drain(). --HPS _

Re: Kernel panic from lagg_ioctl and lagg_port_ioctl

2016-01-13 Thread Lakshmi Narasimhan Sundararajan
Hi Hans, Yes, we understand that piece of code. But Panasas wants this change to MFC to 10.3. This issue is not seen in 11. Would that happen? I have not seen acknowledgement of this issue or confirmation of MFC to 10.3. That information will help us plan. Regards, LN On Wed, Jan 13, 2016 at 6:0

Re: Kernel panic from lagg_ioctl and lagg_port_ioctl

2016-01-13 Thread Hans Petter Selasky
On 01/12/16 22:13, Lewis, Fred wrote: In earlier versions of lagg_ioctl() (e.g. stable/10/r171247) all of the callout vectors are set to NULL which I think will prevent the problem. Similar NULLing code is also in stable/7. I didn't check other releases. Don't forget to drain the callouts befo

Kernel panic from lagg_ioctl and lagg_port_ioctl

2016-01-12 Thread Lewis, Fred
Hi FreeBSD Networking folks. We are seeing a kernel panics on stable/10 that are being caused by lagg_ioctl() and lagg_port_ioctl(). The panic occurs when moving from an lacp configuration to, say, a failover configuration. Please double-check me, but what appears to be happening is that the so

Kernel panic from lagg_ioctl and lagg_port_ioctl

2016-01-12 Thread Lewis, Fred
Hi FreeBSD Networking folks. We are seeing a kernel panics on stable/10 that are being caused by lagg_ioctl() and lagg_port_ioctl(). The panic occurs when moving from an lacp configuration to, say, a failover configuration. Please double-check me, but what appears to be happening is that the soft