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
| ||
|
Date: Thu, 27 Jul 2017 10:04:37 +0300 From: Moni Shoua <monis@...lanox.com> To: Yuval Shaia <yuval.shaia@...cle.com> Cc: Marcel Apfelbaum <marcel@...hat.com>, linux-rdma <linux-rdma@...r.kernel.org>, Linux Kernel Mailinglist <linux-kernel@...r.kernel.org>, Doug Ledford <dledford@...hat.com>, Sean Hefty <sean.hefty@...el.com>, Hal Rosenstock <hal.rosenstock@...il.com> Subject: Re: [PATCH] drivers/rxe: improve rxe loopback On Wed, Jul 26, 2017 at 10:57 PM, Yuval Shaia <yuval.shaia@...cle.com> wrote: > On Wed, Jul 26, 2017 at 05:52:48PM +0300, Marcel Apfelbaum wrote: >> Currently a packet is marked for loopback only if the source and >> destination address match. This is not enough when multiple >> gids are present in rxe's gid table and the traffic is >> from one gid to another. >> >> Fix it by marking the packet for loopback if the destination >> address appears in rxe's gid table. >> >> Signed-off-by: Marcel Apfelbaum <marcel@...hat.com> > Have you considered using ip_route_output_key() for IPv4 or ip6_route_output() for IPv6 to decide if this is a loopback? For reference you can check the flow starting at rdma_resolve_ip()
Powered by blists - more mailing lists