mirror of
https://github.com/Fishwaldo/Star64_linux.git
synced 2025-07-23 23:32:14 +00:00
writeback: Avoid iput() from flusher thread
Doing iput() from flusher thread (writeback_sb_inodes()) can create problems because iput() can do a lot of work - for example truncate the inode if it's the last iput on unlinked file. Some filesystems depend on flusher thread progressing (e.g. because they need to flush delay allocated blocks to reduce allocation uncertainty) and so flusher thread doing truncate creates interesting dependencies and possibilities for deadlocks. We get rid of iput() in flusher thread by using the fact that I_SYNC inode flag effectively pins the inode in memory. So if we take care to either hold i_lock or have I_SYNC set, we can get away without taking inode reference in writeback_sb_inodes(). As a side effect of these changes, we also fix possible use-after-free in wb_writeback() because inode_wait_for_writeback() call could try to reacquire i_lock on the inode that was already free. Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
This commit is contained in:
parent
dbd5768f87
commit
169ebd9013
4 changed files with 65 additions and 23 deletions
|
@ -530,7 +530,13 @@ static void evict(struct inode *inode)
|
|||
|
||||
inode_sb_list_del(inode);
|
||||
|
||||
inode_sync_wait(inode);
|
||||
/*
|
||||
* Wait for flusher thread to be done with the inode so that filesystem
|
||||
* does not start destroying it while writeback is still running. Since
|
||||
* the inode has I_FREEING set, flusher thread won't start new work on
|
||||
* the inode. We just have to wait for running writeback to finish.
|
||||
*/
|
||||
inode_wait_for_writeback(inode);
|
||||
|
||||
if (op->evict_inode) {
|
||||
op->evict_inode(inode);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue