diff options
| author | Mike Snitzer <snitzer@redhat.com> | 2018-12-11 21:31:40 +0300 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2018-12-11 23:19:26 +0300 |
| commit | f6c367585d0d851349d3a9e607c43e5bea993fa1 (patch) | |
| tree | 5f9f861489c47f376ae85b7b942f6a231aca0c02 /lib/memory-notifier-error-inject.c | |
| parent | d57f9da890696af1484f4a47f7f123560197865a (diff) | |
| download | linux-f6c367585d0d851349d3a9e607c43e5bea993fa1.tar.xz | |
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 'lib/memory-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions