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
| ||
|
Message-ID: <20170511165659.GB20043@lst.de> Date: Thu, 11 May 2017 18:56:59 +0200 From: "hch@....de" <hch@....de> To: Ursula Braun <ubraun@...ux.vnet.ibm.com> Cc: "hch@....de" <hch@....de>, Sagi Grimberg <sagi@...mberg.me>, Bart Van Assche <Bart.VanAssche@...disk.com>, "davem@...emloft.net" <davem@...emloft.net>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org> Subject: Re: net/smc and the RDMA core On Thu, May 11, 2017 at 06:50:04PM +0200, Ursula Braun wrote: > Please consider the following patch to make users aware of the > security implications through existing mechanisms. Any such patch would be in addition to the BROKEN marker until there is an actual alternative. > + rmb_desc->mr_rx[SMC_SINGLE_LINK] = > + lgr->lnk[SMC_SINGLE_LINK].roce_pd->__internal_mr; And it's named __internal_mr for reason. The right interface to use the unsafe rkey is to use pd->unsafe_global_rkey.
Powered by blists - more mailing lists