Comment 11 for bug 2039719

The description of lp2039719-2-multipathd-fix-check_path-errors-with-removed-map.patch says:

> Looking through the current kernel code, I can't see any reason why a reinstate would fail, where a reload would help.

Could you please confirm that the relevant kernel code isn't different in the Focal release kernel? Since the kernel ABI is stable, but inferring the ABI from a snapshot of the code doesn't necessarily follow. This seems unlikely so I won't block accepting this to proposed on this though.

> Continuously add and remove all the individual paths for storage devices in order to create and remove multipath devices managed by multipathd...

Unless I misunderstand, could you please clarify the steps you are using to do this?

Minor observation: debian/patches/lp2042366-dm_get_map-fix-segfault-when-can-t-found-target.patch is different in Focal, but only in metadata.