mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-11-08 03:33:25 -05:00
| Filename | Latest commit message | Latest commit date |
|---|---|---|
1ba50bbe93
the two places inside exofs that where taking the BKL were:
exofs_put_super() - .put_super
and
exofs_sync_fs() - which is .sync_fs and is also called from
.write_super.
Now exofs_sync_fs() is protected from itself by also taking
the sb_lock.
exofs_put_super() directly calls exofs_sync_fs() so there is no
danger between these two either.
In anyway there is absolutely nothing dangerous been done
inside exofs_sync_fs().
Unless there is some subtle race with the actual lifetime of
the super_block in regard to .put_super and some other parts
of the VFS. Which is highly unlikely.
Signed-off-by: Boaz Harrosh <[email protected]>
Signed-off-by: Al Viro <[email protected]>
|
||
| .. | ||
| BUGS | ||
| common.h | ||
| dir.c | ||
| exofs.h | ||
| file.c | ||
| inode.c | ||
| Kbuild | ||
| Kconfig | ||
| namei.c | ||
| osd.c | ||
| super.c | ||
| symlink.c | ||