All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: prashant@broadcom.com, mchan@broadcom.com,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH][v3.18.y][v3.19.y]  tg3: Hold tp->lock before calling tg3_halt() from tg3_init_one()
Date: Fri, 06 Mar 2015 15:17:28 -0500	[thread overview]
Message-ID: <54FA0B58.3040806@canonical.com> (raw)
In-Reply-To: <54F8CDDE.6090002@canonical.com>

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@ce.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



      reply	other threads:[~2015-03-06 20:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 21:42 [PATCH][v3.18.y][v3.19.y] tg3: Hold tp->lock before calling tg3_halt() from tg3_init_one() Joseph Salisbury
2015-03-06 20:17 ` Joseph Salisbury [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54FA0B58.3040806@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=prashant@broadcom.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.