Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Reuben Farrelly <reuben-lkml@reub.net>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>,
	neilb@suse.de, linux-kernel@vger.kernel.org,
	Alan Stern <stern@rowland.harvard.edu>,
	linux-scsi@vger.kernel.org
Subject: Re: 2.6.14-mm1
Date: Wed, 09 Nov 2005 13:30:53 +1300	[thread overview]
Message-ID: <4371433D.3080402@reub.net> (raw)
In-Reply-To: <1131459667.3270.8.camel@mulgrave>



Hi,

On 9/11/2005 3:21 a.m., James Bottomley wrote:
> On Mon, 2005-11-07 at 10:52 -0800, Andrew Morton wrote:
>> sd_issue_flush() has been altered to run scsi_disk_get_from_dev(), which
>> takes a semaphore.  It does this from within spinlock and, as we see here,
>> from within softirq.
>>
>> Methinks the people who developed and tested that patch forgot to enable
>> CONFIG_PREEMPT, CONFIG_DEBUG_KERNEL, CONFIG_DEBUG_SLAB,
>> CONFIG_DEBUG_SPINLOCK and CONFIG_DEBUG_SPINLOCK_SLEEP.
> 
> Actually, I do too (as far as I can on non-x86).  I assume you also need
> a filesystem that excites this, though.
> 
> Try the attached: We can probably rely on the block device having opened
> the sd device, so there should already be a reference held on the
> scsi_disk ... well that's my theory and I'm sticking to it.
> 
> James
> 
> diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
> --- a/drivers/scsi/sd.c
> +++ b/drivers/scsi/sd.c
> @@ -769,20 +769,16 @@ static void sd_end_flush(request_queue_t
>  static int sd_prepare_flush(request_queue_t *q, struct request *rq)
>  {
>  	struct scsi_device *sdev = q->queuedata;
> -	struct scsi_disk *sdkp = scsi_disk_get_from_dev(&sdev->sdev_gendev);
> -	int ret = 0;
> +	struct scsi_disk *sdkp = dev_get_drvdata(&sdev->sdev_gendev);
>  
> -	if (sdkp) {
> -		if (sdkp->WCE) {
> -			memset(rq->cmd, 0, sizeof(rq->cmd));
> -			rq->flags |= REQ_BLOCK_PC | REQ_SOFTBARRIER;
> -			rq->timeout = SD_TIMEOUT;
> -			rq->cmd[0] = SYNCHRONIZE_CACHE;
> -			ret = 1;
> -		}
> -		scsi_disk_put(sdkp);
> -	}
> -	return ret;
> +	if (!sdkp || !sdkp->WCE)
> +		return 0;
> +
> +	memset(rq->cmd, 0, sizeof(rq->cmd));
> +	rq->flags |= REQ_BLOCK_PC | REQ_SOFTBARRIER;
> +	rq->timeout = SD_TIMEOUT;
> +	rq->cmd[0] = SYNCHRONIZE_CACHE;
> +	return 1;
>  }
>  
>  static void sd_rescan(struct device *dev)

Yup, with that patch it all works now.  Thanks James!

FWIW, the filesystem on the raid md's is a reiserfs (reiserfs v3 that is).

reuben

      reply	other threads:[~2005-11-09  0:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051106182447.5f571a46.akpm@osdl.org>
     [not found] ` <436F2452.9020207@reub.net>
     [not found]   ` <20051107020905.69c0b6dc.akpm@osdl.org>
     [not found]     ` <17263.11214.992300.34384@cse.unsw.edu.au>
     [not found]       ` <20051107023723.5cf63393.akpm@osdl.org>
     [not found]         ` <436F3020.1040209@reub.net>
2005-11-07 18:52           ` 2.6.14-mm1 Andrew Morton
2005-11-07 19:27             ` 2.6.14-mm1 Alan Stern
2005-11-07 21:43             ` 2.6.14-mm1 J.A. Magallon
2005-11-08  0:07               ` 2.6.14-mm1 J.A. Magallon
2005-11-08 14:21             ` 2.6.14-mm1 James Bottomley
2005-11-09  0:30               ` Reuben Farrelly [this message]

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=4371433D.3080402@reub.net \
    --to=reuben-lkml@reub.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=stern@rowland.harvard.edu \
    /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