Messages in this thread | | | Subject | Re: 2.4 status page, lightly updated | Date | Fri, 28 Jul 2000 14:48:26 +0100 (BST) | From | Alan Cox <> |
| |
> > Audit all char and block drivers to ensure they are safe with the 2.3 > > locking - a lot of them are not especially on the open() path. > > What about the open() path? They have (or grab) BKL there, so it should > not be something special. Now, read() and write()...
They dont all get open right either ;) And yes a lot get read/write wrong or assume incorrectly that single opener == single threaded read/write.
> > Stick lock_kernel() calls around driver with issues to hard to fix nicely > > for 2.4 itself > ???
(eg the OSS sound which I've done - OSS runs under the big kernel lock, its simply too foul to correct)
> > File locking needs checking for races > ? Which locking? flock() or VFS one?
flock/lockf. Willy was/is working on this
- 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/
| |