netdev - Re: [PATCH net-next v6 4/5] ice: add ability to read and configure FW log data

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]

Date: Thu, 14 Dec 2023 15:15:08 -0800
From: Paul M Stillwell Jr <paul.m.stillwell.jr@...el.com>
To: "Keller, Jacob E" <jacob.e.keller@...el.com>, "Nguyen, Anthony L"
	<anthony.l.nguyen@...el.com>, "davem@...emloft.net" <davem@...emloft.net>,
	"kuba@...nel.org" <kuba@...nel.org>, "pabeni@...hat.com" <pabeni@...hat.com>,
	"edumazet@...gle.com" <edumazet@...gle.com>, "netdev@...r.kernel.org"
	<netdev@...r.kernel.org>
CC: "Tipireddy, Vaishnavi" <vaishnavi.tipireddy@...el.com>, "horms@...nel.org"
	<horms@...nel.org>, "leon@...nel.org" <leon@...nel.org>, "Pucha, HimasekharX
 Reddy" <himasekharx.reddy.pucha@...el.com>
Subject: Re: [PATCH net-next v6 4/5] ice: add ability to read and configure FW
 log data

On 12/14/2023 2:12 PM, Keller, Jacob E wrote:
> 
> 
>> -----Original Message-----
>> From: Nguyen, Anthony L <anthony.l.nguyen@...el.com>
>> Sent: Thursday, December 14, 2023 11:41 AM
>> To: davem@...emloft.net; kuba@...nel.org; pabeni@...hat.com;
>> edumazet@...gle.com; netdev@...r.kernel.org
>> Cc: Stillwell Jr, Paul M <paul.m.stillwell.jr@...el.com>; Nguyen, Anthony L
>> <anthony.l.nguyen@...el.com>; Keller, Jacob E <jacob.e.keller@...el.com>;
>> Tipireddy, Vaishnavi <vaishnavi.tipireddy@...el.com>; horms@...nel.org;
>> leon@...nel.org; Pucha, HimasekharX Reddy
>> <himasekharx.reddy.pucha@...el.com>
>> Subject: [PATCH net-next v6 4/5] ice: add ability to read and configure FW log data
> ...
> 
>> +/* the order in this array is important. it matches the ordering of the
>> + * values in the FW so the index is the same value as in ice_fwlog_level
>> + */
>> +static const char * const ice_fwlog_log_size[] = {
>> +	"128K",
>> +	"256K",
>> +	"512K",
>> +	"1M",
>> +	"2M",
>> +};
> 
> The comment feels like a copy paste. The size should only matter for software and shouldn't have anything to do with he firmware as this is just the size of the buffer we'll allocate to store into?
> 

Yeah, not sure how that got in there...

> Thanks,
> Jake