[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <94D0CD8314A33A4D9D801C0FE68B402958CCCE2C@G4W3202.americas.hpqcorp.net>
Date: Fri, 3 Oct 2014 18:16:26 +0000
From: "Elliott, Robert (Server Storage)" <Elliott@...com>
To: Christoph Hellwig <hch@...radead.org>,
Douglas Gilbert <dgilbert@...erlog.com>
CC: SCSI development list <linux-scsi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
James Bottomley <james.bottomley@...senpartnership.com>,
Milan Broz <gmazyland@...il.com>
Subject: RE: [PATCH] scsi_debug: deadlock between completions and surprise
module removal
> -----Original Message-----
> From: linux-scsi-owner@...r.kernel.org [mailto:linux-scsi-
> owner@...r.kernel.org] On Behalf Of Christoph Hellwig
> Sent: Thursday, 25 September, 2014 7:13 AM
> To: Douglas Gilbert
> Cc: SCSI development list; linux-kernel; James Bottomley; Christoph Hellwig;
> Milan Broz
> Subject: Re: [PATCH] scsi_debug: deadlock between completions and surprise
> module removal
>
> Review ping again?
>
> While I think the shutdown code in scsi_debug needs a bit more of an
> overhault I'd really like to include the fix at least for 3.18 and
> 3.17-stable now that we have missed the 3.17 window.
>
> On Sun, Aug 31, 2014 at 07:09:59PM -0400, Douglas Gilbert wrote:
> > A deadlock has been reported when the completion
> > of SCSI commands (simulated by a timer) was surprised
> > by a module removal. This patch removes one half of
> > the offending locks around timer deletions. This fix
> > is applied both to stop_all_queued() which is were
> > the deadlock was discovered and stop_queued_cmnd()
> > which has very similar logic.
> >
> > This patch should be applied both to the lk 3.17 tree
> > and Christoph's drivers-for-3.18 tree.
> >
> > Tested-and-reported-by: Milan Broz <gmazyland@...il.com>
> > Signed-off-by: Douglas Gilbert <dgilbert@...erlog.com>
Reviewed-by: Robert Elliott <elliott@...com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists