aboutsummaryrefslogtreecommitdiff
path: root/crypto/rmd256.c
diff options
context:
space:
mode:
authorAlan D. Brunelle <alan.brunelle@hp.com>2009-08-07 12:01:08 -0400
committerJens Axboe <jens.axboe@oracle.com>2009-08-12 18:50:08 +0200
commit39cbb602b543e477df71dca84b5b2e36f8bd29fc (patch)
tree70639084b6a04ce428cecbaa5fa30c2d71d5ff33 /crypto/rmd256.c
parent7cb7beb31aa3d941833b6a6e553687422c31e4b6 (diff)
Remove double removal of blktrace directory
commit fd51d251e4cdb21f68e9dbc4336514d64a105a79 Author: Stefan Raspl <raspl@linux.vnet.ibm.com> Date: Tue May 19 09:59:08 2009 +0200 blktrace: remove debugfs entries on bad path added in an explicit invocation of debugfs_remove for bt->dir, in blk_remove_buf_file_callback we are also getting the directory removed. On occasion I am seeing memory corruption that I have bisected down to this commit. [The testing involves a (long) series of I/O benchmarks with blktrace invoked around the actual runs.] I believe that this committed patch is correct, but the problem actually lies in the code in blk_remove_buf_file_callback. With this patch I am able to consistently get complete runs whereas previously I could not get a single run to complete. The first part of the patch simply moves the debugfs_remove below the relay_close: the relay_close call will remove files under bt->dir, and so we should not remove the directory until all the files we created have been removed. (Note: This is not sufficient to fix the problem - the file system code has ref counts on the directoy, so our invocation does not cause the directory to actually be removed. Nonetheless, we should not rely upon that feature.) Signed-off-by: Alan D. Brunelle <alan.brunelle@hp.com> Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Diffstat (limited to 'crypto/rmd256.c')
0 files changed, 0 insertions, 0 deletions