Removable IDE devices problem
Quoted 8 lines
Your analysis of the problem is entierly right, since the current kernel behaviour for removable media is supposed to work for floppies (never get this thing out of your computer
as long as long the diode blinks) or read only media where it doesn't really matter. However I still don't see a good way to resolve this issue. (Maybe just adding buffer cache flush before going into thecheck_media_changebusiness of "grocking" partitions would be sufficient...
But there is ide-floppy and ide-cd with their own media_check functions.
I'm thinking about ignoring the removable bit, at least when the device does not have door lock. What would be hurt by it?
P.S. Sorry for the previous mail with long lines. I should know better than using Outlook...
Quoted 9 lines · Marko Kohtala
Quoted 8 lines
Your analysis of the problem is entierly right, since the current kernel behaviour for removable media is supposed to work for floppies (never get this thing out of your computer
as long as long the diode blinks) or read only media where it doesn't really matter. However I still don't see a good way to resolve this issue. (Maybe just adding buffer cache flush before going into thecheck_media_changebusiness of "grocking" partitions would be sufficient...
Quoted 3 lines
But there is ide-floppy and ide-cd with their own
media_checkfunctions.I'm thinking about ignoring the removable bit, at least when the device does not have door lock. What would be hurt by it?
I have currently already just compared the ways invalidate_device() is used in different linux block device drivers. And guess what... The way it get's currently used in ide code are bogous. This will changed soon and should help your problems. (Soon means - if the weather doesn't remain good over this weekend ;-). However please feel free to have a look after this yourself.