David Teigland 01156de6f7 lvmcache: add optional dev arg to lvmcache_info_from_pvid ... A number of places are working on a specific dev when they call lvmcache_info_from_pvid() to look up an info struct based on a pvid. In those cases, pass the dev being used to lvmcache_info_from_pvid(). When a dev is specified, lvmcache_info_from_pvid() will verify that the cached info it's using matches the dev being processed before returning the info. Calling code will not mistakenly get info for the wrong dev when duplicate devs exist. This confusion was happening when scanning labels when duplicate devs existed. label_read for the first dev would add an info struct to lvmcache for that dev/pvid. label_read for the second dev would see the pvid in lvmcache from first dev, and mistakenly conclude that the label_read from the second dev can be skipped because it's already been done. By verifying that the dev for the cached pvid matches the dev being read, this mismatch is avoided and the label is actually read from the second duplicate.		2016-06-07 15:15:47 -05:00
..
label.c	lvmcache: add optional dev arg to lvmcache_info_from_pvid	2016-06-07 15:15:47 -05:00
label.h	doc: change fsf address	2016-01-21 12:11:37 +01:00