summaryrefslogtreecommitdiff
path: root/include/net
diff options
context:
space:
mode:
authorNikos Tsironis <ntsironis@arrikto.com>2021-02-11 17:22:43 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-03-04 11:39:58 +0300
commitfc204c6b398378a70d79cbac24cd16cce412a0c7 (patch)
tree92b5e0fc00233e10638d482195450421182d80db /include/net
parent5ccfc76e5e0b3e7aa54e23568d2184c31b8a777f (diff)
downloadlinux-fc204c6b398378a70d79cbac24cd16cce412a0c7.tar.xz
dm era: only resize metadata in preresume
commit cca2c6aebe86f68103a8615074b3578e854b5016 upstream. Metadata resize shouldn't happen in the ctr. The ctr loads a temporary (inactive) table that will only become active upon resume. That is why resize should always be done in terms of resume. Otherwise a load (ctr) whose inactive table never becomes active will incorrectly resize the metadata. Also, perform the resize directly in preresume, instead of using the worker to do it. The worker might run other metadata operations, e.g., it could start digestion, before resizing the metadata. These operations will end up using the old size. This could lead to errors, like: device-mapper: era: metadata_digest_transcribe_writeset: dm_array_set_value failed device-mapper: era: process_old_eras: digest step failed, stopping digestion The reason of the above error is that the worker started the digestion of the archived writeset using the old, larger size. As a result, metadata_digest_transcribe_writeset tried to write beyond the end of the era array. Fixes: eec40579d84873 ("dm: add era target") Cc: stable@vger.kernel.org # v3.15+ Signed-off-by: Nikos Tsironis <ntsironis@arrikto.com> Signed-off-by: Mike Snitzer <snitzer@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include/net')
0 files changed, 0 insertions, 0 deletions