ient and match well with my specific use case I can live without it and I
don't think the size cost is significant enough to matter. I expect to get some
feedback from other developers in the coming months regarding my Linux 3.4
integration but I doubt it would change my current opinion on the matt
On Aug 8, 2012, at 11:35 PM, Milan Broz wrote:
> On 08/09/2012 02:40 AM, Wesley Miaw wrote:
>>
>>
>> This isn't as polished because I pretty much just added support to do
>> what I needed. I'm not sure if the LKML is the right place to post,
>> so let me kno
On Aug 8, 2012, at 11:35 PM, Milan Broz wrote:
On 08/09/2012 02:40 AM, Wesley Miaw wrote:
This isn't as polished because I pretty much just added support to do
what I needed. I'm not sure if the LKML is the right place to post,
so let me know if I should send this somewhere else
case I can live without it and I
don't think the size cost is significant enough to matter. I expect to get some
feedback from other developers in the coming months regarding my Linux 3.4
integration but I doubt it would change my current opinion on the matter.
Thanks,
--
Wesley Miaw
On Aug 8, 2012, at 1:56 PM, Milan Broz wrote:
> On 08/08/2012 10:46 PM, Wesley Miaw wrote:
>
>> I did modify veritysetup on my own so the format and verify commands will
>> work with regular files on disk instead of having to mount through loop
>> devices.
>
>
ent version number is
what would be used to detect if the data offset option is supported. Thanks.
From: Wesley Miaw
Add data device start block index as optional dm-verity target parameters to
support verity targets where the data does not begin at sector 0 of the block
device.
Also fix the hash blo
On Aug 8, 2012, at 1:56 PM, Milan Broz wrote:
> On 08/08/2012 10:46 PM, Wesley Miaw wrote:
>
>> I did modify veritysetup on my own so the format and verify commands will
>> work with regular files on disk instead of having to mount through loop
>> devices.
>
>
e
last-block boundary check so I will re-submit my patch with that as well.
I did modify veritysetup on my own so the format and verify commands will work
with regular files on disk instead of having to mount through loop devices.
--
Wesley Miaw
signature.asc
Description: Message signed with OpenPGP using GPGMail
From: Wesley Miaw
Add data device start block index to dm-verity target parameters to support
verity targets where the data does not begin at sector 0 of the block device.
Also fix the hash block index computation so it takes into account data offsets.
Signed-off-by: Wesley Miaw
From: Wesley Miaw wm...@netflix.com
Add data device start block index to dm-verity target parameters to support
verity targets where the data does not begin at sector 0 of the block device.
Also fix the hash block index computation so it takes into account data offsets.
Signed-off-by: Wesley
with that as well.
I did modify veritysetup on my own so the format and verify commands will work
with regular files on disk instead of having to mount through loop devices.
--
Wesley Miaw
signature.asc
Description: Message signed with OpenPGP using GPGMail
On Aug 8, 2012, at 1:56 PM, Milan Broz wrote:
On 08/08/2012 10:46 PM, Wesley Miaw wrote:
I did modify veritysetup on my own so the format and verify commands will
work with regular files on disk instead of having to mount through loop
devices.
Which veritysetup? In upstream (cryptsetup
is supported. Thanks.
From: Wesley Miaw wm...@netflix.com
Add data device start block index as optional dm-verity target parameters to
support verity targets where the data does not begin at sector 0 of the block
device.
Also fix the hash block index computations so they take into account any
On Aug 8, 2012, at 1:56 PM, Milan Broz wrote:
On 08/08/2012 10:46 PM, Wesley Miaw wrote:
I did modify veritysetup on my own so the format and verify commands will
work with regular files on disk instead of having to mount through loop
devices.
Which veritysetup? In upstream (cryptsetup
to the hash
block index computation.
Patch and (hopefully proper) commit message below. Thanks.
--
Wesley Miaw
Add data device start block index to dm-verity target parameters to support
verity targets where the data does not begin
to the hash
block index computation.
Patch and (hopefully proper) commit message below. Thanks.
--
Wesley Miaw
Add data device start block index to dm-verity target parameters to support
verity targets where the data does not begin
16 matches
Mail list logo
