netdev - Re: [RFC PATCH 1/1] bna: Generic Netlink Interface to collect FW trace

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]

Message-ID: <BANLkTimOuF+HtLxsmTGVpC7ahU_NFy_L2g@mail.gmail.com>
Date:	Thu, 28 Apr 2011 10:51:27 -0700
From:	Debashis Dutt <debdut@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	shemminger@...tta.com, rmody@...cade.com, netdev@...r.kernel.org,
	huangj@...cade.com, amathur@...cade.com, ddutt@...cade.com
Subject: Re: [RFC PATCH 1/1] bna: Generic Netlink Interface to collect FW trace

On Tue, Apr 26, 2011 at 7:17 PM, David Miller <davem@...emloft.net> wrote:
> From: Debashis Dutt <debdut@...il.com>
> Date: Tue, 26 Apr 2011 19:16:29 -0700
>
>> However, since the generic netlink is a more generic interface, we could use
>> this infrastructure in the driver for commands which are not part of
>> other standard tools.
>
> You aren't the only device in the world that might want to provide
> a facility to fetch firmware traces.
>
> This isn't really a niche thing specific to your device at all.
>

David,

Agreed.

In that case should we use debugfs for collecting f/w trace,
but use generic netlink for other h/w specific commands?

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