netdev - Re: [net-next 05/15] i40e: add a comment on barrier and fix panic on reset

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: <52CEB538.50505@cogentembedded.com>
Date:	Thu, 09 Jan 2014 18:42:00 +0400
From:	Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To:	Jeff Kirsher <jeffrey.t.kirsher@...el.com>, davem@...emloft.net
CC:	Greg Rose <gregory.v.rose@...el.com>, netdev@...r.kernel.org,
	gospo@...hat.com, sassmann@...hat.com,
	Mitch Williams <mitch.a.williams@...el.com>,
	Jesse Brandeburg <jesse.brandeburg@...el.com>
Subject: Re: [net-next 05/15] i40e: add a comment on barrier and fix panic
 on reset

Hello.

On 09-01-2014 16:52, Jeff Kirsher wrote:

> From: Greg Rose <gregory.v.rose@...el.com>

> The memory barrier used in maybe_stop_tx can use a comment.

> Also add checks to VSI->rx_rings to ensure a kernel panic is not induced.

    Don't see why this is made in one patch instead of two since the two 
things look completely unrelated and even modifying different files.

> Change-ID: I48cc1bf1d6cf301818155b737edeef77c0d790c7
> Change-ID: I1363a8445fbf521a26267849966296ed55f43ad8

    Why even 2 of them?

> Signed-off-by: Greg Rose <gregory.v.rose@...el.com>
> Signed-off-by: Mitch Williams <mitch.a.williams@...el.com>
> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@...el.com>
> Tested-by: Kavindya Deegala <kavindya.s.deegala@...el.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>

WBR, Sergei

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