netdev - Re: [PATCH net-next 2/9] net: Remove e_inval label from ip_route_input

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20150923.111959.295309376360736446.davem@davemloft.net>
Date:	Wed, 23 Sep 2015 11:19:59 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dsa@...ulusnetworks.com
Cc:	alexander.duyck@...il.com, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 2/9] net: Remove e_inval label from
 ip_route_input_slow

From: David Ahern <dsa@...ulusnetworks.com>
Date: Wed, 23 Sep 2015 12:03:03 -0600

> They add a lot of value. They make each change very easy to follow. No
> one is going to pickup a single patch in this series and backport to
> some kernel. Each is dependent on the one before it. Given that I
> would rather waste a few steps and ensure I arrive at the destination
> without error.

The problem is that people will, in the future, have the backport bug
fixes _THROUGH_ all of these code rearrangements.

And the person who is going to have to do that, is _ME_.

And if that kind of pain is going to be bestowed upon me, it has to
be for something of great value.

I do not see great value in your rearrangements here, not at all.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html