diff options
| author |   Bruno Faccini <bruno.faccini@intel.com> | 2016-06-20 16:55:27 -0400 |
|---|---|---|
| committer |   Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2016-06-20 14:28:39 -0700 |
| commit | c9cc8d0f6f770635b206784686a16157db3d43b8 (patch) | |
| tree | f96ac61072f315556f6479783957fde99bb6f95a /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | staging/lustre/llite: Get rid of ll_lock_dcache/ll_unlock_dcache (diff) | |
| download | linux-dev-c9cc8d0f6f770635b206784686a16157db3d43b8.tar.xz linux-dev-c9cc8d0f6f770635b206784686a16157db3d43b8.zip | |
staging/lustre/llite: lock i_lock before __d_drop()
There has been several Lustre Client crashes reported by sites
running with Lustre versions 2.1/2.5, all showing the same
dentry->d_hash->next corrupted pointer cause.
This patch fixes a regression that has been introduced since a
long time by commit :
(LU-506 kernel: FC15 - support dcache scalability changes.)
where i_lock protection usage has been removed and
that is likely to cause racy condition during dentry [un]hashing
and to be the root cause of these crashes.
Signed-off-by: Bruno Faccini <bruno.faccini@intel.com>
Reviewed-on: http://review.whamcloud.com/19287
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7973
Reviewed-by: Lai Siyao <lai.siyao@intel.com>
Reviewed-by: Yang Sheng <yang.sheng@intel.com>
Signed-off-by: Oleg Drokin <green@linuxhacker.ru>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions