linux-kernel - Re: [PATCH][v3.18.y][v3.19.y] tg3: Hold tp->lock before calling tg3_halt() from tg3_init

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: <54FA0B58.3040806@canonical.com>
Date:	Fri, 06 Mar 2015 15:17:28 -0500
From:	Joseph Salisbury <joseph.salisbury@...onical.com>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	prashant@...adcom.com, mchan@...adcom.com,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH][v3.18.y][v3.19.y]  tg3: Hold tp->lock before calling
 tg3_halt() from tg3_init_one()

On 03/05/2015 04:42 PM, Joseph Salisbury wrote:
> Hello,
>     
> Please consider including mainline commit
> d0af71a3573f1217b140c60b66f1a9b335fb058b in the next v3.18.y and v3.19.y
> stable releases.  It was included in the mainline tree as of v4.0-rc1. 
> It has been tested and confirmed to resolve:
> http://bugs.launchpad.net/bugs/1428111 .
>
> This commit fixes a regression introduced going from 3.16 to 3.19, so it
> may not be needed in earlier than 3.18 stable releases.
>
> commit d0af71a3573f1217b140c60b66f1a9b335fb058b
> Author: Jun'ichi Nomura \(NEC\) <j-nomura@...jp.nec.com>
> Date:   Thu Feb 12 01:26:24 2015 +0000
>
>     tg3: Hold tp->lock before calling tg3_halt() from tg3_init_one()
>
>
> Sincerely,
> Joseph Salisbury
>
>

After some further testing, it looks like only 3.19 is affected by the
bug.  The upstream 3.18.y stable kernel does not require the commit.

Thanks,

Joe


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/