obj-$(CONFIG_NFP_NETVF) += nfp_netvf.o nfp_netvf-objs := \ nfp_net_common.o \ nfp_net_ethtool.o \ nfp_net_offload.o \ nfp_netvf_main.o ifeq ($(CONFIG_BPF_SYSCALL),y) nfp_netvf-objs += \ nfp_bpf_verifier.o \ nfp_bpf_jit.o endif nfp_netvf-$(CONFIG_NFP_NET_DEBUG) += nfp_net_debugfs.o s-private-remove' type='application/atom+xml'/>
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFilipe Manana <fdmanana@suse.com>2016-11-24 02:09:04 +0000
committerFilipe Manana <fdmanana@suse.com>2016-11-25 18:06:50 +0000
commit8d9eddad19467b008e0c881bc3133d7da94b7ec1 (patch)
tree59713176da0ae96b4f0b53afe000201657382907
parentf177d73949bf758542ca15a1c1945bd2e802cc65 (diff)
Btrfs: fix qgroup rescan worker initialization
We were setting the qgroup_rescan_running flag to true only after the rescan worker started (which is a task run by a queue). So if a user space task starts a rescan and immediately after asks to wait for the rescan worker to finish, this second call might happen before the rescan worker task starts running, in which case the rescan wait ioctl returns immediatley, not waiting for the rescan worker to finish. This was making the fstest btrfs/022 fail very often. Fixes: d2c609b834d6 (btrfs: properly track when rescan worker is running) Cc: stable@vger.kernel.org # 4.4+ Signed-off-by: Filipe Manana <fdmanana@suse.com> Reviewed-by: David Sterba <dsterba@suse.com>