Skip to contentSkip to conversation

struct char_device

PATCH [email protected] 2 participants 2 messages May 23, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 3 lines
Quoted 1 line
	dev_t rdev;

Reasonable.

Good. We all agree.
(But now you see what I meant in comments about mknod.)

Quoted 3 lines
Quoted 1 line
	kdev_t dev;

Useless. If you hope that block_device will help to solve rmmod races

Yes. Why am I mistaken?

Andries

#1 lore raw
Quoted 4 lines · On Wed, 23 May 2001 [email protected] wrote:
Quoted 3 lines
Quoted 1 line
	dev_t rdev;

Reasonable.

Quoted 8 lines

Good. We all agree.
(But now you see what I meant in comments about mknod.)

Quoted 3 lines
Quoted 1 line
	kdev_t dev;

Useless. If you hope that block_device will help to solve rmmod races

Yes. Why am I mistaken?

Because the problems begin in subsystems. Solving the situation with block_device_operations is trivial. It's stuff on the character side that is going to bite you big way. TTY drivers, for example. They are below the layer where your kdev_t lives.