Date: Thu, 16 Jun 2016 20:05:48 -0700 From: Matt Joras <matt.joras@gmail.com> To: Alan Somers <asomers@freebsd.org>, Sean Bruno <sbruno@freebsd.org> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: lagg(4): LOR, deadlock and panic Message-ID: <1466132748.8545.5.camel@gmail.com> In-Reply-To: <CAOtMX2jHHJjW6gsXvYWNdqzq0ms0p0dYBFjSZLP3jfwahRGRMw@mail.gmail.com> References: <459d2639-b490-beee-9cd4-05f38983eaed@freebsd.org> <CAOtMX2jHHJjW6gsXvYWNdqzq0ms0p0dYBFjSZLP3jfwahRGRMw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2016-06-14 at 09:26 -0600, Alan Somers wrote: > > I don't know the best answer either. But while you're in there, are > you interested in fixing any other lagg panics too? I've written > some > ATF torture tests for lagg, but I haven't checked them into head yet > because most of them quickly panic. > > -Alan We run into if_lagg and if_vlan panics at $WORK all the time in our automation. I've fixed the if_vlan panics and I'm hoping to update this review: https://reviews.freebsd.org/D5825 soon with something that accomodates drivers sleeping in the vlan_*config event handlers (which involves having a global rmlock _and_ sx in if_vlan). I was planning on doing a similar audit/fixing of if_lagg soon when I get the chance. Matt Joras
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1466132748.8545.5.camel>