netdev - Re: [PATCH] tipc: fix endianness on tipc subscriber messages

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20100308.153811.109635961.davem@davemloft.net>
Date:	Mon, 08 Mar 2010 15:38:11 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	allan.stephens@...driver.com
Cc:	nhorman@...driver.com, netdev@...r.kernel.org
Subject: Re: [PATCH] tipc: fix endianness on tipc subscriber messages

Allan, I don't think you're being reasonable at all.

You tell Neil he's breaking things, and that his code isn't following
the current spec.

Neil asks where the spec is.

And you tell him your out-of-tree code is the spec.

That's absolutely rediculious.  It is totally unreasonable to require
Neil to unravel the mess that is the out-of-tree TIPC implementation
in order to figure out what the current protocol "spec" is.

You're doing a lot of "oh crap, don't do this, you'll break this or
that."  But frankly, you really don't care what's in the upstream
kernel.  If you did, your stuff wouldn't be out of tree.

Therefore I take every piece of feedback you give to Neil's
patches with a grain of salt, at best.
--
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