netdev - Re: [PATCH net-next 0/3] Improve tracing at the driver/core boundary

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20140114.144723.957109797286173047.davem@davemloft.net>
Date:	Tue, 14 Jan 2014 14:47:23 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	bhutchings@...arflare.com
Cc:	netdev@...r.kernel.org, linux-net-drivers@...arflare.com
Subject: Re: [PATCH net-next 0/3] Improve tracing at the driver/core
 boundary

From: Ben Hutchings <bhutchings@...arflare.com>
Date: Fri, 10 Jan 2014 22:15:39 +0000

> These patches add static tracpeoints at the driver/core boundary which
> record various skb fields likely to be useful for datapath debugging.
> On the TX side the boundary is where the core calls ndo_start_xmit, and
> on the RX side it is where any of the various exported receive functions
> is called.
> 
> The set of skb fields is mostly based on what I thought would be
> interesting for sfc.
> 
> These patches are basically the same as what I sent as an RFC in
> November, but rebased.  They now depend on 'net: core: explicitly select
> a txq before doing l2 forwarding', so please merge net into net-next
> before trying to apply them.  The first patch fixes a code formatting
> error left behind after that fix.

This looks great, series applied, thanks Ben.
--
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