Re: [PATCH 0/7] safe implementation of loop reuse

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jul 14, 2016 at 03:28:11PM +0200, Stanislav Brabec wrote:
> That is why I wrote new implementation that should be safe.
> 
> To keep the code as small as possible, it changes API of several
> functions: it adds sizelimit check possibility.

Merged, I did some changes to the code. The most visible change is
that loopcxt_find_overlap() (originally loopcxt_check_conflict())
returns info about full match (offset and sizelimit matches). 

This allows to use just one iteration (loopdevs scan) in mount(8) to
check for overlaps as well as to found device to re-use.

All works as expected, but re-test if you can :-)

Tomorrow I'm going to work on the losetup patches.

    Karel


-- 
 Karel Zak  <kzak@xxxxxxxxxx>
 http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux