summaryrefslogtreecommitdiffstats
path: root/fs/gfs2
diff options
context:
space:
mode:
authorOmar Sandoval <osandov@fb.com>2019-09-16 11:30:57 -0700
committerDavid Sterba <dsterba@suse.com>2019-11-18 12:46:48 +0100
commita0cac0ec961f0d42828eeef196ac2246a2f07659 (patch)
treeac1a1a6f5e7770b0a9e3cbcf2aa3e448a56a6078 /fs/gfs2
parent57d4f0b863272ba04ba85f86bfdc0f976f0af91c (diff)
downloadlinux-a0cac0ec961f0d42828eeef196ac2246a2f07659.tar.gz
linux-a0cac0ec961f0d42828eeef196ac2246a2f07659.tar.bz2
linux-a0cac0ec961f0d42828eeef196ac2246a2f07659.zip
btrfs: get rid of unique workqueue helper functions
Commit 9e0af2376434 ("Btrfs: fix task hang under heavy compressed write") worked around the issue that a recycled work item could get a false dependency on the original work item due to how the workqueue code guarantees non-reentrancy. It did so by giving different work functions to different types of work. However, the fixes in the previous few patches are more complete, as they prevent a work item from being recycled at all (except for a tiny window that the kernel workqueue code handles for us). This obsoletes the previous fix, so we don't need the unique helpers for correctness. The only other reason to keep them would be so they show up in stack traces, but they always seem to be optimized to a tail call, so they don't show up anyways. So, let's just get rid of the extra indirection. While we're here, rename normal_work_helper() to the more informative btrfs_work_helper(). Reviewed-by: Nikolay Borisov <nborisov@suse.com> Reviewed-by: Filipe Manana <fdmanana@suse.com> Signed-off-by: Omar Sandoval <osandov@fb.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/gfs2')
0 files changed, 0 insertions, 0 deletions