From: Tomas Henzl <thenzl@redhat.com>
To: Vinson Lee <vlee@twopensource.com>
Cc: Greg KH <greg@kroah.com>,
Masoud Sharbiani <msharbiani@twopensource.com>,
stable@vger.kernel.org, Don Brace <Don.Brace@pmcs.com>,
JBottomley@parallels.com, linux-scsi@vger.kernel.org
Subject: Re: Backport of a fix for HPSA (Disabling a disabled device problem during kdump) driver
Date: Mon, 13 Apr 2015 15:18:44 +0200 [thread overview]
Message-ID: <552BC234.4020000@redhat.com> (raw)
In-Reply-To: <CAHTgTXU1GV8JszqJojk9ML7f1yEtERHY0VjrnjX+OMh4Z_=t0g@mail.gmail.com>
On 04/11/2015 12:45 AM, Vinson Lee wrote:
> On Tue, Jan 27, 2015 at 4:18 PM, Greg KH <greg@kroah.com> wrote:
>> On Tue, Jan 06, 2015 at 05:15:19PM +0100, Tomas Henzl wrote:
>>> On 01/05/2015 07:41 PM, Masoud Sharbiani wrote:
>>>> Dear stable maintainers,
>>>> Can you please backport commitid 132aa220b45d60e9b20def1e9d8be9422eed9616
>>>> (hpsa: refine the pci enable/disable handling) to 3.10 stable (and
>>>> earlier, if applicable)?
>>> Please do not apply this patch isolated from his friend, the
>>> 859c75aba20264d87dd026bab0d0ca3bff385955 hpsa: add missing pci_set_master in kdump path
>>> needs to be applied together with the 132aa220b45d60e9b20def1e9d8be9422eed9616 .
>>>
>>> In addition to that, after the original issue goes away you may notice sometimes
>>> an unhandled irq 16 message, to fix this a patch is posted
>>> here http://www.spinics.net/lists/linux-scsi/msg80316.html
>>> This patch still awaits a maintainers review though.
>>>
>>> Probably the best idea is to wait until the issue is solved completely.
>> I'll wait, when it all gets worked out, please let stable@ know what
>> patches to apply where.
>>
>> thanks,
>>
>> greg k-h
>> --
>> To unsubscribe from this list: send the line "unsubscribe stable" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> Hi, Thomas.
>
> The unhandled irq 16 issue seems to be fixed by 4.0-rc1 commit "hpsa:
> turn off interrupts when kdump starts".
>
> Are the following patches suitable for stable now?
Yes, I believe they are, just note that
03741d9 hpsa: fix memory leak in kdump hard reset
is not a part of that group we discussed before, but it may be added
to stable too.
Cheers,
Tomas
>
> 3b74729 hpsa: turn off interrupts when kdump starts
> 03741d9 hpsa: fix memory leak in kdump hard reset
> 859c75a hpsa: add missing pci_set_master in kdump path
> 132aa22 hpsa: refine the pci enable/disable handling
>
> Cheers,
> Vinson
next prev parent reply other threads:[~2015-04-13 13:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 18:41 Backport of a fix for HPSA (Disabling a disabled device problem during kdump) driver Masoud Sharbiani
2015-01-06 16:15 ` Tomas Henzl
2015-01-28 0:18 ` Greg KH
2015-04-10 22:45 ` Vinson Lee
2015-04-13 13:18 ` Tomas Henzl [this message]
2015-04-16 16:03 ` Luis Henriques
2015-04-26 9:27 ` Greg KH
2015-04-27 12:17 ` Tomas Henzl
2015-04-27 12:55 ` Greg KH
2015-04-27 13:10 ` Tomas Henzl
2015-05-02 17:56 ` Greg KH
2015-05-22 19:19 ` Vinson Lee
2015-05-26 11:02 ` Jiri Slaby
2015-06-15 3:33 ` Zefan Li
2015-06-30 0:09 ` Greg KH
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=552BC234.4020000@redhat.com \
--to=thenzl@redhat.com \
--cc=Don.Brace@pmcs.com \
--cc=JBottomley@parallels.com \
--cc=greg@kroah.com \
--cc=linux-scsi@vger.kernel.org \
--cc=msharbiani@twopensource.com \
--cc=stable@vger.kernel.org \
--cc=vlee@twopensource.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;
as well as URLs for NNTP newsgroup(s).