aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorScott Mayhew <[email protected]>2017-12-15 16:12:32 -0500
committerTrond Myklebust <[email protected]>2018-01-14 23:06:29 -0500
commitba4a76f703ab7eb72941fdaac848502073d6e9ee (patch)
treed2a7374a5b6e01c3f34f94230e8533c3a0a19616 /tools/perf/scripts/python/export-to-postgresql.py
parentb3dce6a2f0601be9b6781b394fdf6ceb63009a44 (diff)
nfs/pnfs: fix nfs_direct_req ref leak when i/o falls back to the mds
Currently when falling back to doing I/O through the MDS (via pnfs_{read|write}_through_mds), the client frees the nfs_pgio_header without releasing the reference taken on the dreq via pnfs_generic_pg_{read|write}pages -> nfs_pgheader_init -> nfs_direct_pgio_init. It then takes another reference on the dreq via nfs_generic_pg_pgios -> nfs_pgheader_init -> nfs_direct_pgio_init and as a result the requester will become stuck in inode_dio_wait. Once that happens, other processes accessing the inode will become stuck as well. Ensure that pnfs_read_through_mds() and pnfs_write_through_mds() clean up correctly by calling hdr->completion_ops->completion() instead of calling hdr->release() directly. This can be reproduced (sometimes) by performing "storage failover takeover" commands on NetApp filer while doing direct I/O from a client. This can also be reproduced using SystemTap to simulate a failure while doing direct I/O from a client (from Dave Wysochanski <[email protected]>): stap -v -g -e 'probe module("nfs_layout_nfsv41_files").function("nfs4_fl_prepare_ds").return { $return=NULL; exit(); }' Suggested-by: Trond Myklebust <[email protected]> Signed-off-by: Scott Mayhew <[email protected]> Fixes: 1ca018d28d ("pNFS: Fix a memory leak when attempted pnfs fails") Cc: [email protected] Signed-off-by: Trond Myklebust <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions