mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Jinu M." <jinum@esntechnologies.co.in>
Cc: linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org,
	surendrai@esntechnologies.co.in
Subject: Re: removable media support on 2.6.x
Date: Fri, 4 Jun 2004 21:47:39 -0700	[thread overview]
Message-ID: <20040604214739.61232c26.akpm@osdl.org> (raw)
In-Reply-To: <1118873EE1755348B4812EA29C55A9722AF016@esnmail.esntechnologies.co.in>

"Jinu M." <jinum@esntechnologies.co.in> wrote:
>
> Hi All,
> 
> We are developing a storage driver (block driver) on 2.6.x kernel. The 
> hardware we are using supports media removal on the fly. We are facing
> some problem when the media is removed while the disk is mounted. The
> system freezes and the module count never goes to zero.
> 
> This is what we do when the disk is removed on the fly.
> 
> disk_removed(...)
> {
> 	/* invalidate disk */
> 	if(gDisk->bdev) {
> 		invalidate_bdev(gDisk->bdev, 1);
> 		bdput(gDisk->bdev);
> 	}
> 
> 	/* indicates that no disk present */
> 	set_capacity(gDisk->gd, 0);
> 
> 	/* cleanup gendisk */
> 	del_gendisk(gDisk->gd);
> 	put_disk(gDisk->gd);
> 
> 	/* clean up blkqueue */
> 	blk_cleanup_queue(gDisk->blkqueue);
> }
> 
> disk_removed() is called from the workqueue that is initiated from the
> tasklet()<=isr() on card removal.
> 
> We guess invalidate_bdev() is the culprit ;) but would like to know
> from you all if we are doing some mistake. Is there something missing
> or something wrong in the way we are trying to provide removable media
> support?
> 

afaik we don't really support hot unplug like this.

Changes were made a few months ago (make the VFS use file->f_mapping rather
than file->f_dentry->d_inode->i_mapping) which set some of the pieces in
place but I think there's a way to go yet.

umm, the general idea is that when the disk vanishes your driver should
then return -EIO for all future I/O requests.  The block_device, the queue,
the inode and all that stuff remains in-core.

After device hot unplug we need to do <something> to disassociate the
defunct blockdev inode from the /dev/hdXX node.  I think <something> hasn't
been coded yet.

Later, someone puts in new media and you can then access that via /dev/hdXX
- you get a brand new inode, blockdev, queue, etc.  The old defunct one is
still alive, returning -EIO.

Eventually, all references to the old inode/blockdev/queue go away (due to
applications hitting EIO, etc).  The old mountpoint can be unmounted and
this drops the final ref, so the old inode/blockdev/queue get freed up.

As I say, I don't think all of this is implemented yet, but perhaps a lot
of it is.

  reply	other threads:[~2004-06-05  4:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 15:11 Jinu M.
2004-06-05  4:47 ` Andrew Morton [this message]
2004-06-05 21:33   ` modprobing ACPI(?) module gives oops (2.6.7-rc2-mm2) Grzegorz Kulewski
2004-06-05  5:08 removable media support on 2.6.x Jinu M.
2004-06-05 10:51 ` Matthias Urlichs

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=20040604214739.61232c26.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=jinum@esntechnologies.co.in \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=surendrai@esntechnologies.co.in \
    /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

all inboxes | Powered by JetHome®