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: Wed, 2 Nov 2016 18:29:00 +0300 From: Cyrill Gorcunov <gorcunov@...il.com> To: David Ahern <dsa@...ulusnetworks.com> Cc: netdev@...r.kernel.org, Eric Dumazet <eric.dumazet@...il.com>, "David S. Miller" <davem@...emloft.net>, Andrey Vagin <avagin@...nvz.org>, Stephen Hemminger <stephen@...workplumber.org> Subject: Re: [patch net-next 0/2] Fixes for raw diag sockets handling On Wed, Nov 02, 2016 at 09:10:32AM -0600, David Ahern wrote: > > @__dif != 0 the match may return socket where sk_bound_dev_if = 0 > > instead of completely matching one. Isn't it? > > yes. I recently added an exact_dif to the lookup for listener sockets > (see compute_score). Something like that could be added to INET_MATCH. Seem so. I need to revisit this moment. Because with current lookup code iproute2 patches I made and been testing do not kill all sockets bound to particular device in one pass (because request from userspace asks for index 15 in my case but kernel return one with index 0). At first I thought I made a mistake in userspace code but once I added printk's into kernel I found that here some strange results over lookup. Cyrill
Powered by blists - more mailing lists