VLAN interface management - unloading carrying driver hangs the
machine
Jack Vogel
jfvogel at gmail.com
Thu Jan 8 01:09:17 PST 2009
Fine with me, go do it and I'll take the driver code out :)
Jack
On Thu, Jan 8, 2009 at 12:18 AM, Yony Yossef <yonyossef.lists at gmail.com>wrote:
> > Jack Vogel wrote:
> > >
> > >
> > > On Wed, Jan 7, 2009 at 9:54 AM, Sam Leffler <sam at freebsd.org
> > > <mailto:sam at freebsd.org>> wrote:
> > >
> > > Yony Yossef wrote:
> > >
> > > Yony Yossef wrote:
> > >
> > >
> > > /sbin/ifconfig vlan3653 create
> > >
> > > Problem is when I assign an IP to the vlan
> > interface.
> > > In that case, unloading the driver results
> > in hanging
> > > the host.
> > > Does it sound familiar to anybody?
> > >
> > >
> > > Well, surely I'd expect problems by doing so.
> > > The correct way is to
> > >
> > > /sbin/ifconfig vlan3653 destroy
> > >
> > > before unloading the driver.
> > >
> > > Angelo.
> > >
> > >
> > >
> > > Thanks, I didn't know freebsd does not allow it.
> > >
> > >
> > >
> > > This seems wrong. Someone should disallow the driver
> > > detach/unload. Please file a PR about this so the issue
> > is not lost.
> > >
> > > Sam
> > >
> > >
> > > In many drivers, ahem, like mine, there is a test at detach and it
> > > will not allow it if there is a non-NULL trunk.
> > >
> > > Sounds like a broken driver needs to be fixed is all...
> > >
> > I don't agree; drivers should not be required to deal with
> > this. If someone files a PR and assigns it to me I'll look at it.
> >
> > Sam
> >
>
> I agree with Sam. There's no reason to leave this check to the driver.
>
> Yony
>
>
More information about the freebsd-net
mailing list