diff options
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/filesystems/Locking | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/Documentation/filesystems/Locking b/Documentation/filesystems/Locking index ec6a9392a173..4e78ce677843 100644 --- a/Documentation/filesystems/Locking +++ b/Documentation/filesystems/Locking | |||
| @@ -437,8 +437,11 @@ grab BKL for cases when we close a file that had been opened r/w, but that | |||
| 437 | can and should be done using the internal locking with smaller critical areas). | 437 | can and should be done using the internal locking with smaller critical areas). |
| 438 | Current worst offender is ext2_get_block()... | 438 | Current worst offender is ext2_get_block()... |
| 439 | 439 | ||
| 440 | ->fasync() is a mess. This area needs a big cleanup and that will probably | 440 | ->fasync() is called without BKL protection, and is responsible for |
| 441 | affect locking. | 441 | maintaining the FASYNC bit in filp->f_flags. Most instances call |
| 442 | fasync_helper(), which does that maintenance, so it's not normally | ||
| 443 | something one needs to worry about. Return values > 0 will be mapped to | ||
| 444 | zero in the VFS layer. | ||
| 442 | 445 | ||
| 443 | ->readdir() and ->ioctl() on directories must be changed. Ideally we would | 446 | ->readdir() and ->ioctl() on directories must be changed. Ideally we would |
| 444 | move ->readdir() to inode_operations and use a separate method for directory | 447 | move ->readdir() to inode_operations and use a separate method for directory |