Re: Route messages



Mike Tancsa wrote:
I am thinking

http://lists.freebsd.org/pipermail/cvs-src/2008-April/090303.html
is the commit ? If I revert to the prev version, the issue goes away.

Yes, this change doesn't look right. It should only do the route
lookup in ip_input.c when there was an EMSGSIZE error returned by
ip_output(). The rtalloc_ign() call causes the message to be sent
because it always sets report to one. The default message is RTM_MISS.

I'll try to prep an updated patch which doesn't have these issues later
today.

--
Andre
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: Route messages
    ... is the commit? ... If I revert to the prev version, ... If you do that, do not do an extra route lookup if possible, correct ...
    (freebsd-net)
  • Re: Route messages
    ... is the commit? ... If I revert to the prev version, ... If you do that, do not do an extra route lookup if possible, correct ...
    (freebsd-net)
  • Re: Route messages
    ... is the commit? ... If I revert to the prev version, ... If you do that, do not do an extra route lookup if possible, correct ...
    (freebsd-net)
  • Re: Route messages
    ... is the commit? ... If I revert to the prev version, ... If you do that, do not do an extra route lookup if possible, correct ...
    (freebsd-net)
  • Re: 2.6.29-rc1 does not boot and fails to resume
    ... Revert this commit also solves problem on my laptoop. ... but that is subtly problematic from a lock hierarchy POV: ... u32 val; ...
    (Linux-Kernel)

Loading