diff options
| author | NeilBrown <[email protected]> | 2018-02-23 09:09:33 +1100 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2018-02-27 14:45:10 +0100 |
| commit | 17556cdbe6ed70a6a20e597b228628f7f34387f8 (patch) | |
| tree | d7ccc50776fdef4feaeaff8cd0044ebce862297f /tools/perf/scripts/python/bin | |
| parent | 01220025b14ab6be3d41313b45e87be332f217e4 (diff) | |
staging: lustre: lmv: correctly iput lmo_root
Commit 8f18c8a48b73 ("staging: lustre: lmv: separate master object
with master stripe") changed how lmo_root inodes were managed,
particularly when LMV_HASH_FLAG_MIGRATION is not set.
Previously lsm_md_oinfo[0].lmo_root was always a borrowed
inode reference and didn't need to by iput().
Since the change, that special case only applies when
LMV_HASH_FLAG_MIGRATION is set
In the upstream (lustre-release) version of this patch [Commit
60e07b972114 ("LU-4690 lod: separate master object with master
stripe")] the for loop in the lmv_unpack_md() was changed to count
from 0 and to ignore entry 0 if LMV_HASH_FLAG_MIGRATION is set.
In the patch that got applied to Linux, that change was missing,
so lsm_md_oinfo[0].lmo_root is never iput().
This results in a "VFS: Busy inodes" warning at unmount.
Fixes: 8f18c8a48b73 ("staging: lustre: lmv: separate master object with master stripe")
Signed-off-by: NeilBrown <[email protected]>
Reviewed-by: James Simmons <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions