diff options
| author | Mikulas Patocka <mpatocka@redhat.com> | 2020-01-13 23:04:37 +0300 |
|---|---|---|
| committer | Mike Snitzer <snitzer@redhat.com> | 2020-01-15 04:22:51 +0300 |
| commit | 873937e75f9a8ea231a502c3d29d9cb6ad91b3ef (patch) | |
| tree | eeec0ff6835692a45d16b9016466f62bf7124b86 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | a4a8d286586d4b28c8517a51db8d86954aadc74b (diff) | |
| download | linux-873937e75f9a8ea231a502c3d29d9cb6ad91b3ef.tar.xz | |
dm thin: don't allow changing data device during thin-pool reload
The existing code allows changing the data device when the thin-pool
target is reloaded.
This capability is not required and only complicates device lifetime
guarantees. This can cause crashes like the one reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=1788596
where the kernel tries to issue a flush bio located in a structure that
was already freed.
Take the first step to simplifying the thin-pool's data device lifetime
by disallowing changing it. Like the thin-pool's metadata device, the
data device is now set in pool_create() and it cannot be changed for a
given thin-pool.
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions