netdev - Re: [PATCH net-next 00/15] net/smc: Shared Memory Communications

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-next>] [day] [month] [year] [list]

Message-Id: <20160607.150725.893789208195156330.davem@davemloft.net>
Date:	Tue, 07 Jun 2016 15:07:25 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ubraun@...ux.vnet.ibm.com
Cc:	netdev@...r.kernel.org, linux-s390@...r.kernel.org,
	schwidefsky@...ibm.com, heiko.carstens@...ibm.com,
	utz.bacher@...ibm.com
Subject: Re: [PATCH net-next 00/15] net/smc: Shared Memory Communications -
 RDMA

In case my previous reply wasn't clear enough, I require that you provide
a more accurate description of what the implications of this feature are.

Namely, that important _CORE_ networking features are completely bypassed
and unusable when SMC applies to a connection.

Specifically, all packet shaping, filtering, traffic inspection, and
flow management facilitites in the kernel will not be able to see nor
act upon the data flow of these TCP connections once established.

It is always important, and in my opinion required, to list the
negative aspects of your change and not just the "wow, amazing"
positive aspects.

Thanks.