netdev - Re: [net-next 0/9][pull request] Intel Wired LAN Driver Updates 2015-03-09

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: <20150309.160510.1331119766701559402.davem@redhat.com>
Date:	Mon, 09 Mar 2015 16:05:10 -0400 (EDT)
From:	David Miller <davem@...hat.com>
To:	jeffrey.t.kirsher@...el.com
Cc:	netdev@...r.kernel.org, nhorman@...hat.com, sassmann@...hat.com,
	jogreene@...hat.com
Subject: Re: [net-next 0/9][pull request] Intel Wired LAN Driver Updates
 2015-03-09

From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Date: Mon,  9 Mar 2015 10:55:33 -0700

> This series contains updates to i40e and i40evf.
> 
> Greg cleans up some "hello world" strings which were left around from
> early development.
> 
> Shannon modifies the drive to make sure the sizeof() calls are taking
> the size of the actual struct that we care about.  Also updates the
> NVMUpdate read/write so that it is less noisy when logging.  This was
> because the NVMUpdate tool does not necessarily know the ReadOnly map of
> the current NVM image, and must try reading and writing words that may be
> protected.  This generates an error out of the Firmware request that the
> driver logs.  Unfortunately, this ended up spitting out hundreds of
> bogus read/write error messages.  If a user wants the noisy logging,
> the change can be overridden by enabling the NVM update debugging.
> 
> Mitch fixes a possible deadlock issue where if a reset occurred when the
> netdev is closed, the reset task will hang in napi_disable.  Added
> ethtool RSS support as suggested by Ben Hutchings.
> 
> Jesse fixes a bug introduced in the force writeback code, where the
> interrupt rate was set to 0 (maximum) by accident.  The driver must
> correctly set the NOITR fields to avoid IT update as a side effect
> of triggering the software interrupt.
> 
> I provided a simple cleanup to make the use of PF/VF consistent, which
> was reported by Joe Perches.

Pulled, thanks Jeff.
--
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