From: Jason Andryuk <jason.p.andryuk@aero.org>
To: "Roger Pau Monné" <roger.pau@citrix.com>, xen-devel@lists.xen.org
Cc: david.vrabel@citrix.com
Subject: Re: Missed Stable backport? maybe [PATCH v2 0/4] xen-blk: bug fixes
Date: Fri, 20 Jun 2014 12:34:07 -0400 [thread overview]
Message-ID: <53A4627F.9080107@aero.org> (raw)
In-Reply-To: <53A44F57.3070507@citrix.com>
On 6/20/2014 11:12 AM, Roger Pau Monné wrote:
> On 20/06/14 16:32, Jason Andryuk wrote:
>> Hi Roger,
>>
>> I'm seeing a crash on shutdown in xen_blkbk_unmap on 3.12.22. kdb backtrace below. Could this be the shutdown race fixed by "[PATCH v2 3/4] xen-blkback: fix shutdown race"? That email does not provide the observed backtrace, so I cannot compare.
>
> Could be related, but you didn't provide the reason for the crash, just
> the backtrace, have you tried applying those patches on top of your kernel?
The backtrace was seen rebooting my box. kdb is configured in the hardware domain, so it broke into that. Not all guests were shutdown prior to the restart.
It's intermittent. I just rebooted ready to capture the serial log, but there was no crash.
I haven't tried the patches yet. They came up when googling for related error messages. I hope to try them soon.
Regards,
Jason
>> The cover letter for "[PATCH v2 0/4] xen-blk: bug fixes" <Message-Id: 1391509575-3949-1-git-send-email-roger.pau@citrix.com> mentions backport to stable. However, stable was not CC-ed and the patches seem to be missing from linux-stable. Was this just an oversight?
>
> Yes, they are committed to upstream but not stable, I think they should
> all be backported to stable (3.10 and 3.12 AFAICT).
>
> Roger.
>
next prev parent reply other threads:[~2014-06-20 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 14:32 Missed Stable backport? maybe [PATCH v2 0/4] xen-blk: bug fixes Jason Andryuk
2014-06-20 15:12 ` Roger Pau Monné
2014-06-20 16:34 ` Jason Andryuk [this message]
2014-06-23 14:29 ` Jason Andryuk
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=53A4627F.9080107@aero.org \
--to=jason.p.andryuk@aero.org \
--cc=david.vrabel@citrix.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.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.