Re: [issue957] CARP panic

[Petr Janda <elekktretterr@xxxxxxxxxxxxxx>]

Hey,
Can we at least make it an option? if ETHER_INPUT2 is defined use patched 
CARP, if not use the old. I know, a bit of a hack but only temporary.

Cheers,
Petr

On Fri, 11 Jul 2008 11:28:08 am Sepherosa Ziehau wrote:
> Sepherosa Ziehau <sepherosa@gmail.com> added the comment:
>
> Hi,
>
> Using ETHER_INPUT2 is tied with the CARP lock flag changing.  Using
> ETHER_INPUT2 by default is a little bit risky for this release and
> ipflow can't be worked out in compat fashion.  You can just keep the
> patch locally; if you have other NICs that you want to use it with
> CARP, please just tell me.  Currently following NICs has ETHER_INPUT2
> support (so I could test that code path from day to day before release
>
> :)
>
> bge(4) bce(4) em(4) et(4) msk(4) nfe(4) re(4), bfe(4) fxp(4) xl(4)
>
> Once release is done, I will switch to ETHER_INPUT2 in repo; along
> with the CARP lock flag changing of course.
>
> Best Regards,
> sephe
>
> _____________________________________________________
> DragonFly issue tracker <bugs@lists.dragonflybsd.org>
> <https://bugs.dragonflybsd.org/issue957>
> _____________________________________________________