Messages in this thread | | | Date | Sat, 12 Sep 1998 16:38:48 +0100 (GMT Daylight Time) | From | Yiannis Mavroukakis <> | Subject | Re: Bug in mounting routines of atapi-cdroms |
| |
On Sat, 12 Sep 1998, Chris Ricker wrote:
> On Fri, 11 Sep 1998, Erik Andersen wrote: > > > Hmm. It works just fine for me here under 2.1.120. You dont have > > "options cdrom autoclose=0" in /etc/conf.modules, right? Could you try > > adding "options cdrom debug=1" so I can see where the mount process > > dies? The output of dmesg (just the ide and cdrom specific parts) would > > also be useful, so we know what type of drive it is... > > > > -Erik > > The linux cdrom guy > > Erik, > > The problem he's describing sounds like the same one I have that we hunted > down a couple of weeks ago (the changes in fs/isofs/inode.c between 2.1.101 > and 2.1.102). > > Sorry, I'd been meaning to send this to the list since I can't tell from the > Maintainers file who does isofs (is that you, Gordon?) but then got busy > with school and forgot about it. At any rate, the changes to > fs/isofs/inode.c between 2.1.101 and 2.1.102 break cd-rom access for me and > a few other people. They cause mount attempts of the cdrom to hang forever > (on all cds, which work fine under 2.0.x / 2.1.x where x <= 101 , so it's > not a problem with the images being bad). This is still true as of > 2.1.122-pre2. So far, I haven't been able to narrow it down any farther than > that set of changes. Isofs people, please ask away if you need more info., > have magic patches, etc. > /me is no kernel hacker but... i checked isofs.c and found what broke it for me was a typo (possibly)
search for strnicmp and change it to strncmp.that should do the trick.
Cheers, Yiannis.
- 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/faq.html
| |