Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755166AbZFHU7d (ORCPT ); Mon, 8 Jun 2009 16:59:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754552AbZFHU7Q (ORCPT ); Mon, 8 Jun 2009 16:59:16 -0400 Received: from g1t0029.austin.hp.com ([15.216.28.36]:20078 "EHLO g1t0029.austin.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754232AbZFHU7O (ORCPT ); Mon, 8 Jun 2009 16:59:14 -0400 Date: Mon, 8 Jun 2009 15:59:38 -0500 From: scameron@beardog.cca.cpqcorp.net To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, axboe@kernel.dk, akpm@linux-foundation.org Cc: scameron@beardog.cca.cpqcorp.net, mikem@beardog.cca.cpqcorp.net Subject: [patch 1/8] cciss: Use schedule_timeout_uninterruptible in SCSI error handling code Message-ID: <20090608205938.GG23523@beardog.cca.cpqcorp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1161 Lines: 31 Use schedule_timeout_uninterruptible instead of schedule_timeout in the scsi error handling code when waiting between TUR polls since we are not interested in nor want to be interrupted by signals. Signed-off-by: Stephen M. Cameron --- --- diff -puN drivers/block/cciss_scsi.c~use_uninterruptible_timeout drivers/block/cciss_scsi.c --- linux-next/drivers/block/cciss_scsi.c~use_uninterruptible_timeout 2009-06-08 12:56:39.000000000 -0500 +++ linux-next-scameron/drivers/block/cciss_scsi.c 2009-06-08 12:57:17.000000000 -0500 @@ -1608,7 +1608,7 @@ static int wait_for_device_to_become_rea /* Wait for a bit. do this first, because if we send * the TUR right away, the reset will just abort it. */ - schedule_timeout_interruptible(waittime); + schedule_timeout_uninterruptible(waittime); count++; /* Increase wait time with each try, up to a point. */ _ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/