linux-kernel - Re: [dm-devel] [PATCH v4 0/2] Historical Service Time Path Selector

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 21 May 2020 01:26:27 +0200
From:   Xose Vazquez Perez <xose.vazquez@...il.com>
To:     Gabriel Krisman Bertazi <krisman@...labora.com>, agk@...hat.com,
        snitzer@...hat.com
Cc:     breeves@...hat.com, linux-kernel@...r.kernel.org,
        khazhy@...gle.com, song@...nel.org, dm-devel@...hat.com,
        mpatocka@...hat.com, kernel@...labora.com
Subject: Re: [dm-devel] [PATCH v4 0/2] Historical Service Time Path Selector

On 5/11/20 6:39 PM, Gabriel Krisman Bertazi wrote:

> This fourth version of HST applies the suggestion from Mikulas Patocka
> to do the ktime_get_ns inside the mpath map_bio instead of generic
> device-mapper code. This means that struct dm_mpath_io gained another
> 64bit field.  For the request-based case, we continue to use the block
> layer start time information.

You should add some info to the multipath.conf.5 man page ( 
https://git.opensvc.com/gitweb.cgi?p=multipath-tools/.git;a=blob;f=multipath/multipath.conf.5;h=05a5e8ffeb110d969f3b2381eb3b88d7f28380f6;hb=HEAD#l189 ),
or none one is going to use it.


Thanks.