public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Anish Bhatt <anish@chelsio.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Karen Xie <kxie@chelsio.com>,
	Manoj Malviya <manojmalviya@chelsio.com>
Subject: Re: [PATCH scsi] cxgb4i : Avoid holding mutex in interrupt context
Date: Wed, 01 Oct 2014 07:36:45 -0400	[thread overview]
Message-ID: <1412163405.5299.4.camel@jarvis> (raw)
In-Reply-To: <525DB349B3FB5444AE057A887CB2A8D88F78E8@nice.asicdesigners.com>

On Wed, 2014-10-01 at 08:08 +0000, Anish Bhatt wrote:
> James, 
>     This is bugfix  and prevents a "scheduling while atomic" bug that can be
> hit when using an ipv6 address with cxgb4i, and can possibly be seen without
> Chelsio hardware. Could this be cherry picked for 3.17 please ?

Can you describe the bug it's fixing (what are the consequences) and how
often is it seen?

If it's not something everyone hits, it may be better to go via stable,
because the code change is quite large, so validating that nothing else
breaks with it at this stage (a week away from release) is quite
important.

> Christoph,
>    My bad, this is a bugfix for code that was added for 3.17, and I assumed the
> bugfixes would automatically be picked for the next rc. If James doesn't pick 
> this up, I'll send it to stable when appropriate.

You said in your change log:

        Applies on top of core-for-3.18

So the natural assumption would be this is for the merge window queue.

James



  reply	other threads:[~2014-10-01 11:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16  0:44 [PATCH scsi] cxgb4i : Avoid holding mutex in interrupt context Anish Bhatt
2014-09-17 21:00 ` Anish Bhatt
2014-09-22 14:45 ` Christoph Hellwig
2014-10-01  5:22   ` Anish Bhatt
2014-10-01  7:49     ` Christoph Hellwig
2014-10-01  8:08       ` Anish Bhatt
2014-10-01 11:36         ` James Bottomley [this message]
2014-10-01 17:22           ` Karen Xie

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=1412163405.5299.4.camel@jarvis \
    --to=james.bottomley@hansenpartnership.com \
    --cc=anish@chelsio.com \
    --cc=hch@infradead.org \
    --cc=kxie@chelsio.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=manojmalviya@chelsio.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox