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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <C8603108370B1949BF3CC7742DDE5D35B8B39FFD@GSjpTKYDCembx31.service.hitachi.net>
Date:   Thu, 22 Mar 2018 11:58:38 +0000
From:   亀井仁志 / KAMEI,HITOSHI 
        <hitoshi.kamei.xm@...achi.com>
To:     Christoph Hellwig <hch@...radead.org>
CC:     "idryomov@...il.com" <idryomov@...il.com>,
        "sage@...hat.com" <sage@...hat.com>,
        "elder@...nel.org" <elder@...nel.org>,
        "ceph-devel@...r.kernel.org" <ceph-devel@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 2/2] rbd: add 'thick' sysfs rbd device attribute

> The normal storage term would be fully provisioned, not 'thick'

The rbd command, which is user mode program, uses "thick-provision".
If the kernel rbd driver uses "fully provisioned", then the rbd command
should use "fully provisioned" too. 

What do you think, Jason?

Regards,

-- 
Hitoshi Kamei


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ