netdev - Re: Deliver skbs to intermediate interfaces, when using cascaded rx-handlers

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

Date:	Mon, 24 Feb 2014 08:28:29 +0100
From:	Tobias Waldekranz <tobias@...dekranz.com>
To:	David Miller <davem@...emloft.net>
Cc:	jiri@...nulli.us, netdev@...r.kernel.org
Subject: Re: Deliver skbs to intermediate interfaces, when using cascaded
 rx-handlers

On Fri, Feb 21, 2014 at 12:23:59PM -0500, David Miller wrote:
> From: Jiri Pirko <jiri@...nulli.us>
> Date: Fri, 21 Feb 2014 15:48:27 +0100
> 
> > Would not it be better to make DSA better in order to achieve your goal?
> 
> +1

Ok, message received. I will try to merge the changes back into the
mainline DSA infrastructure. I honestly didn't think it would be of
much interest to anyone.

The original question is really separate from that though. In this
case it is a DSA driver at the bottom, but the question applies to any
case where there are multiple rx-handlers in a cascade
configuration. Wouldn't you agree?

-- 
Thanks
 - wkz
--
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