diff options
| author | Mikulas Patocka <mpatocka@redhat.com> | 2020-01-13 15:04:37 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-02-24 08:36:49 +0100 |
| commit | 7f0d9ac2621e93acdf11723a02be4f24e4f01f0c (patch) | |
| tree | 4e4991adec296f237ad9add0cb27152015ca2c73 /drivers/gpio/gpiolib.c | |
| parent | 74f42a77318e8cbf254006c40a6ad3bc53ef6043 (diff) | |
| download | linux-stable-7f0d9ac2621e93acdf11723a02be4f24e4f01f0c.tar.gz linux-stable-7f0d9ac2621e93acdf11723a02be4f24e4f01f0c.tar.bz2 linux-stable-7f0d9ac2621e93acdf11723a02be4f24e4f01f0c.zip | |
dm thin: don't allow changing data device during thin-pool reload
[ Upstream commit 873937e75f9a8ea231a502c3d29d9cb6ad91b3ef ]
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>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/gpio/gpiolib.c')
0 files changed, 0 insertions, 0 deletions