linux-kernel - Re: [PATCH v5 15/17] device-dax: add an 'align' attribute

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] [day] [month] [year] [list]

Date:   Fri, 25 Sep 2020 20:31:24 -0700
From:   Dan Williams <dan.j.williams@...el.com>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     Joao Martins <joao.m.martins@...cle.com>,
        Vishal L Verma <vishal.l.verma@...el.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>,
        Linux MM <linux-mm@...ck.org>,
        linux-nvdimm <linux-nvdimm@...ts.01.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 15/17] device-dax: add an 'align' attribute

On Fri, Sep 25, 2020 at 7:22 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Fri, 25 Sep 2020 12:13:04 -0700 Dan Williams <dan.j.williams@...el.com> wrote:
>
> > Introduce a device align attribute.  While doing so, rename the region
> > align attribute to be more explicitly named as so, but keep it named as
> > @align to retain the API for tools like daxctl.
> >
> > Changes on align may not always be valid, when say certain mappings were
> > created with 2M and then we switch to 1G.  So, we validate all ranges
> > against the new value being attempted, post resizing.
> >
> > Link: https://lkml.kernel.org/r/159643105944.4062302.3131761052969132784.stgit@dwillia2-desk3.amr.corp.intel.com
> > Link: https://lore.kernel.org/r/20200716172913.19658-3-joao.m.martins@oracle.com
> > Signed-off-by: Joao Martins <joao.m.martins@...cle.com>
> > Signed-off-by: Dan Williams <dan.j.williams@...el.com>
> >
>
> The signoff chain implies that this was From:Joao.  Please clarify?

Yes, sorry, my script to squash the fix rewrote the author and I
failed to catch it. This indeed should be:

From: Joao Martins <joao.m.martins@...cle.com>

I double-checked, and it looks like this was the only one in the
series with that problem.