Re: Oops - 2.2.12 [fat]fat_clear_inode+20/2c (gcc 2.95)

Steve Dodd (dirk@loth.demon.co.uk)
Mon, 18 Oct 1999 23:25:31 +0100


[As you set Mail-Followup-To I've not cc'd this to you]

On Mon, Oct 18, 1999 at 03:47:42PM +0100, Simon Huggins wrote:

> I tried to unmout my floppy (fat formatted) and 2.2.12 oops'd on me.
[..]

> Then I got the oops message and umount segfaulted.
> I can reproduce it at will unfortunately. I didn't notice for ages cos
> I normally use zip disks (also fat formatted) which work fine.
>
> This kernel was compiled with gcc 2.95 so I'm not looking for sympathy.
>
> After it segfaulted I probed a bit and tried unmounting it again which
> failed:
[..]

Okay, I dunno anything about the original oops, but I can explain why the
second umount hung. When the first one died it would have been holding at
least the superblock lock, which wouldn't have been released when the process
died. The second one presumably stuck waiting for the superblock lock to be
released.

-- 
"If the bottom is falling out of your world, then have a drink here and
the world will fall out of your bottom."

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/