-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/14/2013 06:07 PM, Andrew Morton wrote:
> huh. What is the user-visible effect of this bug? Just a memory
> leak or something more serious?
Not serious, but user-visible in that the partition devnodes still
show up after detaching the backing
On Sun, 3 Mar 2013 13:49:13 -0500 Phillip Susi wrote:
> Any partitions added by user space to the loop device were being
> left in place after detaching the loop device. This was because
> the detach path issued a BLKRRPART to clean up partitions if
> LO_FLAGS_PARTSCAN was set, meaning that
On Sun, 3 Mar 2013 13:49:13 -0500 Phillip Susi ps...@ubuntu.com wrote:
Any partitions added by user space to the loop device were being
left in place after detaching the loop device. This was because
the detach path issued a BLKRRPART to clean up partitions if
LO_FLAGS_PARTSCAN was set,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/14/2013 06:07 PM, Andrew Morton wrote:
huh. What is the user-visible effect of this bug? Just a memory
leak or something more serious?
Not serious, but user-visible in that the partition devnodes still
show up after detaching the backing
Any partitions added by user space to the loop device were being
left in place after detaching the loop device. This was because
the detach path issued a BLKRRPART to clean up partitions if
LO_FLAGS_PARTSCAN was set, meaning that the partitions were auto
scanned on attach. Replace this BLKRRPART
Any partitions added by user space to the loop device were being
left in place after detaching the loop device. This was because
the detach path issued a BLKRRPART to clean up partitions if
LO_FLAGS_PARTSCAN was set, meaning that the partitions were auto
scanned on attach. Replace this BLKRRPART
6 matches
Mail list logo