archive mirror
 help / color / mirror / Atom feed
From: "Richard Purdie" <>
To: "Alan Cox" <>
Cc: <>
Subject: Re: Flaw in ide_unregister()
Date: Sun, 9 Jan 2005 22:37:20 -0000	[thread overview]
Message-ID: <067d01c4f69b$cb9d8b80$0f01a8c0@max> (raw)
In-Reply-To: 1104674725.14712.50.camel@localhost.localdomain

Alan Cox:
[Re: ide_unregister and problems with ide-cs.c]
> In 2.6.9-ac and 2.6.10-ac the ide_unregister_hwif calls return an error
> if the drive is in use. At this point the ide-cs code still throws it
> away. The -ac code IDE also adds "removed_hwif_iops" so the bits are
> there for the correct result which is something like
> if(ide_unregister_hwif(hwif) < 0 {
> printk("Whine whine...");
> removed_hwif_ops(hwif);
> while(ide_unregister_hwif(hwif) < 0)
> msleep(1000);
> }

I've just tried 2.6.10-ac8 on my target (an arm PDA) and it doesn't help 
ide-cs.c. When I pull out a mounted CF out the socket, the kernel prints 
"Unregister 0 fail 1 0" repeatedly on the console showing the usage count 
permanently stays at 1. This is the same problem as under 2.6.10.

I haven't investigated it yet but I suspect the usage count is held by 
ide-disk as the CF card has a mounted filesystem. As previously mentioned 
and for reference, this patch has the changes I had to make to get standard 
2.6.10 to work:


No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.9 - Release Date: 06/01/2005

  reply	other threads:[~2005-01-09 22:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-31 12:04 Flaw in ide_unregister() Richard Purdie
2005-01-02 14:36 ` Alan Cox
2005-01-09 22:37   ` Richard Purdie [this message]
2005-01-10 11:09     ` Alan Cox
2005-01-10 12:39       ` Richard Purdie
2005-01-10 19:23         ` Alan Cox
2005-01-10 21:17           ` Richard Purdie

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='067d01c4f69b$cb9d8b80$0f01a8c0@max' \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).