svn commit: r204902 - in head/sys: net netinet

[David O'Brien]

On Wed, Mar 10, 2010 at 01:01:06PM -0500, John Baldwin wrote:
> On Wednesday 10 March 2010 11:08:58 am David O'Brien wrote:
> > On Wed, Mar 10, 2010 at 10:50:46AM -0500, John Baldwin wrote:
> > > On Wednesday 10 March 2010 10:23:39 am David O'Brien wrote:
> > > > This change doesn't seem to work in the common case, and has made the
> > > > kernel toxic - with folks unable to connect to 127.0.0.1.  Please back
> > > > this out or adjust the change.
> > > 
> > > Did you try the route.h patch he posted to current@?
> > 
> > I looked at it, and at the diff of his original commit.  The changes were
> > large enough that I don't want to assume his patch takes care of all the
> > issues given that patch hasn't been committed verbatim.
> > 
> > We also have reports of the patch not working in freebsd-current at .
> 
> The reports have all said that the patch fixes pinging 127.0.0.1.  The one 
> problem report is a different situation involving a VPN tunnel.  Just patch 
> your system with the route.h patch for now.

I guess I don't get it - we have got reports of this badly affecting
basic functionallity for several people and yet we wont fix stock
sources?  This is serving users well?

Folks could have applied my patch sent to newvers.sh, but that was calmed
to be so bad that the commit was backed out.  Wow.

-- 
-- David  (obrien at FreeBSD.org)