netdev - Re: HW communication debugging interface

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

Message-ID: <20151005153554.GM2278@nanopsycho.orion>
Date:	Mon, 5 Oct 2015 17:35:54 +0200
From:	Jiri Pirko <jiri@...nulli.us>
To:	John Fastabend <john.fastabend@...il.com>
Cc:	Andrew Lunn <andrew@...n.ch>, "Rosen, Rami" <rami.rosen@...el.com>,
	"davem@...emloft.net" <davem@...emloft.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"eladr@...lanox.com" <eladr@...lanox.com>,
	"idosch@...lanox.com" <idosch@...lanox.com>
Subject: Re: HW communication debugging interface - ideas?

Mon, Oct 05, 2015 at 05:29:09PM CEST, john.fastabend@...il.com wrote:
>On 15-10-05 08:18 AM, Jiri Pirko wrote:
>> Mon, Oct 05, 2015 at 04:58:42PM CEST, andrew@...n.ch wrote:
>>> On Mon, Oct 05, 2015 at 04:55:42PM +0200, Jiri Pirko wrote:
>>>> Mon, Oct 05, 2015 at 04:49:41PM CEST, andrew@...n.ch wrote:
>>>>>>> Are you referring here to messages of the EMAD protocol ?
>>>>>
>>>>> I know nothing about this protocol.....
>>>>>
>>>>> Does it at least use standard Ethernet framing? Source and Destination
>>>>> header and an EtherType which mean EMAD?
>>>>
>>>> Yep, but that does not really matter. I believe we should find debugging
>>>> interface which is protocol agnostic. Just arbitrary messages
>>>> monitoring.
>>>
>>> Hi Jiri
>>>
>>> O.K, it is just that you mentioned wireshark. Passing the frames to
>>> network interface taps would make this trivial.
>> 
>> That is true. But using netlink+nlmon would do the same.
>
>Also I guess if you go this direction you want to make it generic
>enough for any drivers to use it to snoop software/firmware msgs. This
>is common across many devices.

Yes, definitelly, this should be something generic to be usable for
every device type.


>
>In the past though I've just used ethtool dump commands and some
>"scripts" on top of this to debug devices. And when it got really
>bad wrote some throw away code to debug my issue. I guess it might
>be nice to have something in the kernel to improve this but have
>you considered using the tracing features that already exist?

Which ones do you have in mind?


>
>.John
>
>> --
>> 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
>> 
>
--
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