linux-kernel - Re: [PATCH] libnvdimm, dimm: Maximize label transfer size

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:   Fri, 28 Sep 2018 16:03:33 -0700
From:   Dan Williams <dan.j.williams@...el.com>
To:     alexander.h.duyck@...ux.intel.com
Cc:     linux-nvdimm <linux-nvdimm@...ts.01.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] libnvdimm, dimm: Maximize label transfer size

On Fri, Sep 28, 2018 at 3:44 PM Alexander Duyck
<alexander.h.duyck@...ux.intel.com> wrote:
>
> On 9/28/2018 11:56 AM, Dan Williams wrote:
> > Use kvzalloc() to bypass the arbitrary PAGE_SIZE limit of label transfer
> > operations. Given the expense of calling into firmware, maximize the
> > amount of label data we transfer per call to be up to the total label
> > space if allowed by the firmware.
> >
> > Cc: Alexander Duyck <alexander.h.duyck@...ux.intel.com>
> > Signed-off-by: Dan Williams <dan.j.williams@...el.com>
>
> This looks mostly fine to me.
>
> The only thing I am not certain about is if we want to use the raw
> max_cmd_size value or not since there is no guarantee it is aligned to
> any sort of boundary. It might be beneficial to either cache line align
> it or align it to 256B if it is larger than that since that way we at
> least would be getting full labels instead of partial ones.

If we leave any portion of the max transfer size unused it just means
we're that much more likely to need an additional call into the ASL
interpreter. That said It might be worthwhile capping the max transfer
size in case the BIOS specifies something extreme (> 1MB) in the
future.