netdev - Re: [PATCH V4 net-next 0/2] net: implement SMC-R solution

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

Message-Id: <20150825.111849.1251755515298926543.davem@davemloft.net>
Date:	Tue, 25 Aug 2015 11:18:49 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ubraun@...ux.vnet.ibm.com
Cc:	utz.bacher@...ibm.com, netdev@...r.kernel.org,
	linux-s390@...r.kernel.org, schwidefsky@...ibm.com,
	heiko.carstens@...ibm.com, ursula.braun@...ibm.com
Subject: Re: [PATCH V4 net-next 0/2] net: implement SMC-R solution

From: Ursula Braun <ubraun@...ux.vnet.ibm.com>
Date: Fri, 21 Aug 2015 13:30:27 +0200

> this is V4 of my SMC-R patches:
> Since you are asking for a solution "100% in our own separate module
> with our own can of worms", we have to give up the transparent detection
> whether a communication peer can do SMC-R or not (this has been the
> purpose of the rejected TCP hooks). Instead, we want just the new
> self-contained SMC-R socket family added to the kernel.
> By the way, since August 2015 the SMC-R Informational RFC is no longer
> a draft, but published as RFC7609.

The tcp_set_keepalive() layering hack is still beyond what I'm willing
to apply, sorry.

Also, as a coding style note, all of your code needs to be adjusted to
declare local function variables in "reverse christimas tree" order,
that is longest line to shortest.
--
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