Skip to contentSkip to conversation

char/raw.c locking on error

PATCH Bodo Eggert 1 participant 1 message Mar 27, 2009 4 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#4 lore raw
Quoted 6 lines · Jonathan Corbet
Quoted 4 lines · Michael Tokarev

Is it still in use - the raw driver, that is? Nowadays, every block device can be opened in direct mode by using O_DIRECT - this is what raw does. I mean, is it worth spending even more time on it?

As long as you don't fix all the legacy applications to use O_DIRECT.

Quoted 5 lines

This was discussed a while back. My understanding is that there are people using it. It is a user-space ABI of sorts which can't just be yanked arbitrarily. The right thing to do is probably to replace it with a shell implementation that just opens the device using O_DIRECT, but nobody has actually done that...

It had long been done when before it was discussed the last time.