summaryrefslogtreecommitdiffstats
path: root/kernel/async.c
diff options
context:
space:
mode:
authorMike Snitzer <snitzer@redhat.com>2018-12-11 19:31:40 +0100
committerMike Snitzer <snitzer@redhat.com>2018-12-11 21:19:26 +0100
commitf6c367585d0d851349d3a9e607c43e5bea993fa1 (patch)
tree5f9f861489c47f376ae85b7b942f6a231aca0c02 /kernel/async.c
parentdm zoned: Fix target BIO completion handling (diff)
downloadlinux-f6c367585d0d851349d3a9e607c43e5bea993fa1.tar.xz
linux-f6c367585d0d851349d3a9e607c43e5bea993fa1.zip
dm thin: send event about thin-pool state change _after_ making it
Sending a DM event before a thin-pool state change is about to happen is a bug. It wasn't realized until it became clear that userspace response to the event raced with the actual state change that the event was meant to notify about. Fix this by first updating internal thin-pool state to reflect what the DM event is being issued about. This fixes a long-standing racey/buggy userspace device-mapper-test-suite 'resize_io' test that would get an event but not find the state it was looking for -- so it would just go on to hang because no other events caused the test to reevaluate the thin-pool's state. Cc: stable@vger.kernel.org Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'kernel/async.c')
0 files changed, 0 insertions, 0 deletions