Yar Tikhiy writes:
> > Mike Tancsa writes:
> > > >Not sure why this hasn't been detected before though. Below is
> > > >a possible patch.
> > >
> > > It has been at http://www.freebsd.org/cgi/query-pr.cgi?pr=25478 and
> > > discussed a few times in freebsd-net.
> >
> > Here is the better (?) pa
On Wed, Mar 28, 2001 at 11:30:49AM +0400, Yar Tikhiy wrote:
>
> Please take a careful look at the frames 6 through 9 of the stack
> trace in PR#25478, so you may notice that your patch happens to do
> nothing about the broblem. You are going to add a check for IFF_UP
> to ether_output_frame() wh
Hi,
On Tue, Mar 27, 2001 at 12:40:11PM -0800, Archie Cobbs wrote:
> Mike Tancsa writes:
> > >Not sure why this hasn't been detected before though. Below is
> > >a possible patch.
> >
> > It has been at http://www.freebsd.org/cgi/query-pr.cgi?pr=25478 and
> > discussed a few times in freebsd-net
Hi,
On Tue, Mar 27, 2001 at 07:35:24PM -0500, Mike Tancsa wrote:
>
> Any chances for
>
> kern/22176
> kern/22177
> kern/22178
> kern/22179
> kern/22181
>
> These were raised on freebsd-net as well in the thread "A few nasty bugs in
> the networking code"
Thanks to Jordan Hubbard, I've got c
At 12:40 PM 3/27/2001 -0800, Archie Cobbs wrote:
>Mike Tancsa writes:
> > >Not sure why this hasn't been detected before though. Below is
> > >a possible patch.
> >
> > It has been at http://www.freebsd.org/cgi/query-pr.cgi?pr=25478 and
> > discussed a few times in freebsd-net.
>
>Here is the bett
Mike Tancsa writes:
> >Not sure why this hasn't been detected before though. Below is
> >a possible patch.
>
> It has been at http://www.freebsd.org/cgi/query-pr.cgi?pr=25478 and
> discussed a few times in freebsd-net.
Here is the better (?) patch. I'd like to commit this if nobody
objects..
L
