From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= Subject: Re: Missed Stable backport? maybe [PATCH v2 0/4] xen-blk: bug fixes Date: Fri, 20 Jun 2014 17:12:23 +0200 Message-ID: <53A44F57.3070507@citrix.com> References: <53A445F1.9010204@aero.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <53A445F1.9010204@aero.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jason Andryuk , xen-devel@lists.xen.org Cc: david.vrabel@citrix.com List-Id: xen-devel@lists.xenproject.org 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 cover letter for "[PATCH v2 0/4] xen-blk: bug fixes" 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.