| 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: <20151005204056.GA3528@nanopsycho.orion> Date: Mon, 5 Oct 2015 22:40:56 +0200 From: Jiri Pirko <jiri@...nulli.us> To: Marcelo Ricardo Leitner <marcelo.leitner@...il.com> Cc: davem@...emloft.net, netdev@...r.kernel.org, eladr@...lanox.com, idosch@...lanox.com Subject: Re: HW communication debugging interface - ideas? Mon, Oct 05, 2015 at 08:32:33PM CEST, marcelo.leitner@...il.com wrote: >On Wed, Sep 30, 2015 at 03:51:41PM +0200, Jiri Pirko wrote: >> Hi Dave/all. >> >> There is quite common for drivers to speak with HW using "packet-like" >> messages. In our case, we put message into skb and push that out as >> an ordinary packet. HW then sends us reply in a packet, similar to other >> rx-ed packets. > >Better sure than sorry so I'll ask. It's not possible for an application >to inject such skbs somehow, right? Like, a guest, tied to a bridge, >tied to a port which ends up understanding these skbs. No, it's purely for monitoring of communication with HW. > >... >> 2) generic Netlink (genl) interface. Easy to put metadata in, including the >> device identificator (pci address). User then can use nlmon in order to >> be able to use wireshark to see the netlink messages. >> >> Looks like 2) might be viable, well-defined, generic interface to carry >> this info. What do you think? Does this make sense? > >2 seems very interesting, fwiw > > Marcelo -- 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
Powered by blists - more mailing lists