David Teigland aecf542126 metadata: prevent writing beyond metadata area ... lvm uses a bcache block size of 128K. A bcache block at the end of the metadata area will overlap the PEs from which LVs are allocated. How much depends on alignments. When lvm reads and writes one of these bcache blocks to update VG metadata, it can also be reading and writing PEs that belong to an LV. If these overlapping PEs are being written to by the LV user (e.g. filesystem) at the same time that lvm is modifying VG metadata in the overlapping bcache block, then the user's updates to the PEs can be lost. This patch is a quick hack to prevent lvm from writing past the end of the metadata area.		2018-10-29 16:53:17 -05:00
..
label.c	metadata: prevent writing beyond metadata area	2018-10-29 16:53:17 -05:00
label.h	metadata: prevent writing beyond metadata area	2018-10-29 16:53:17 -05:00