netdev - Re: [net-next 04/14] i40e: dump VF information in debugfs

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: <20170420.115153.1510206006505486594.davem@davemloft.net>
Date:   Thu, 20 Apr 2017 11:51:53 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     Yuval.Mintz@...ium.com
Cc:     jiri@...nulli.us, gerlitz.or@...il.com,
        jeffrey.t.kirsher@...el.com, mitch.a.williams@...el.com,
        netdev@...r.kernel.org, nhorman@...hat.com, sassmann@...hat.com,
        jogreene@...hat.com
Subject: Re: [net-next 04/14] i40e: dump VF information in debugfs

From: "Mintz, Yuval" <Yuval.Mintz@...ium.com>
Date: Thu, 20 Apr 2017 13:57:08 +0000

> I agree this surely isn't *our* convention, but for scsi  using debugfs
> [or sysfs] is a common practice for debug purposes.
> 
> Also, our HW debug capabilities are highly-customable, and I want to
> have the ability to configure those on the fly [E.g., dynamically
> configuring various HW events to be recorded].
> Each such configuration involves multiple register writes and reads
> according to user provided inputs.
> I don't really see how to generalize the information collection in a way
> that would benefit anyone else.

That's basically what everyone says who slaps random crap into debugfs.

>> For your inhouse debugging, you should have oot
>> patch to expose whatever you need.
> 
> I don't want in-house debugging capabilities -
> I want field debug capabilities.

Then it has to use a portable, well defined, set of interfaces.