diff options
| author | Alexander Viro <viro@parcelfarce.linux.theplanet.co.uk> | 2003-05-20 07:51:28 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@home.transmeta.com> | 2003-05-20 07:51:28 -0700 |
| commit | a45a6dde99e92061a3aa088fb534aa53b4c4d573 (patch) | |
| tree | f6509d549430ae36674a98f1df2b74eddb887da0 /include/linux | |
| parent | 2d9318a1d530848ce4414c54056d98a2f22c65a6 (diff) | |
[PATCH] O_DIRECT open() fix
Trivial bugfix: opening a file that doesn't have ->direct_IO() with
O_DIRECT passed in flags fails (as it should) but doesn't call
->release() even though ->open() had been successful.
IOW, we have a leak there - e.g. open() of a tty with O_DIRECT will
leak a reference to tty and tty_driver. Besides, quite a few drivers
are _not_ happy with struct file being freed without ->release() after
->open() has returned 0.
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions