netdev - RE: [PATCH net-next 2/5] be2net: Fix to allow setting of debug levels in the firmware.

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

Message-ID: <ab50cee9-d72c-44aa-ba13-9dcff8296a27@exht2.ad.emulex.com>
Date:	Fri, 27 Apr 2012 18:23:22 -0700
From:	<Somnath.Kotur@...lex.Com>
To:	<Somnath.Kotur@...lex.Com>, <bhutchings@...arflare.com>
CC:	<netdev@...r.kernel.org>
Subject: RE: [PATCH net-next 2/5] be2net: Fix to allow setting of debug
 levels in the firmware.

Ben,
 Could you pls respond to my replies inline.

Thanks
Somnath
       

> -----Original Message-----
> From: netdev-owner@...r.kernel.org [mailto:netdev-
> owner@...r.kernel.org] On Behalf Of Somnath.Kotur@...lex.Com
> Sent: Friday, April 27, 2012 12:16 PM
> To: bhutchings@...arflare.com
> Cc: netdev@...r.kernel.org
> Subject: RE: [PATCH net-next 2/5] be2net: Fix to allow setting of debug levels
> in the firmware.
> 
> > > This operation is intended for controlling logging by the driver,
> > > and the flags
> > are defined in <linux/netdevice.h>.  (Not exported to userland yet,
> > but ethtool knows their names.)
> >
> > If your firmware supports some kind of logging then it may be
> > reasonable to have this control both driver and firmware, but not *just*
> the firmware.
> Thanks for your comments Ben.
> 
> Currently the driver logs only a very few critical errors/warnings; so we felt it
> might be an overkill to define driver log levels.
> On the other hand, the F/W has extensive logging and tracing facility and the
> ethtool 'msglevel' option seemed like a reasonable method for controlling
> the logging level.
> 
> >
> > You should also implement the get_msglevel operation at the same time.
> 
> Yes you are correct. We will implement the get_msglevel and re-post the
> patch.
> >
> > Ben.
> >
> 
> Thanks
> Som
> N     r  y   b X  ǧv ^ )޺{.n +   z ^ )   w*jg   .     ݢj/   z ޖ  2 ޙ   & )ߡ a    . G   h . j:+v
> w ٥