public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Doug Ledford <dledford@redhat.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Scsi Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Failure to reread partition tables on non-busy devices
Date: Mon, 18 Nov 2002 11:35:07 +1100	[thread overview]
Message-ID: <3DD835BB.5050608@torque.net> (raw)
In-Reply-To: 20021118000505.GM3280@redhat.com

Doug,
Your patch below fixes the problem I was seeing with fdisk
creating new partitions (on a scsi_debug ram disk) not being
visible outside fdisk.

Doug Gilbert

Doug Ledford wrote:
> This patch (almost certainly wrong BTW) makes it work.  Obviously, 
> somewhere there should be a call to invalidate_bdev(); that doesn't exist.  
> I'm not sure A) where that call should be and B) what checks there should 
> be to avoid calling invalidate_bdev() on a device that is busy.
> 
> fs/partitions/check.c:  1.85 1.86 dledford 02/11/17 17:22:37 (modified, 
> needs delta)
> 
> @@ -453,8 +453,8 @@ int rescan_partitions()
>  	struct parsed_partitions *state;
>  	int p, res;
>  
> -	if (!bdev->bd_invalidated)
> -		return 0;
> +	//if (!bdev->bd_invalidated)
> +	//	return 0;
>  	if (bdev->bd_part_count)
>  		return -EBUSY;
>  	res = invalidate_device(dev, 1);
> 




  reply	other threads:[~2002-11-18  0:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18  0:05 Failure to reread partition tables on non-busy devices Doug Ledford
2002-11-18  0:35 ` Douglas Gilbert [this message]
2002-11-18  0:43 ` Alexander Viro
2002-11-18  3:06   ` Doug Ledford

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=3DD835BB.5050608@torque.net \
    --to=dougg@torque.net \
    --cc=dledford@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox