linux-kernel - Re: RFC: move kernel/memremap.c to mm/

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]

Message-ID: <CAPcyv4g=Hr4KOV1NbzPVRxSVL0TaaEPykG3GHwERjx1-SmUQog@mail.gmail.com>
Date:   Wed, 17 Jul 2019 23:03:49 -0700
From:   Dan Williams <dan.j.williams@...el.com>
To:     Christoph Hellwig <hch@....de>
Cc:     Jason Gunthorpe <jgg@...lanox.com>, Linux MM <linux-mm@...ck.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: RFC: move kernel/memremap.c to mm/

On Wed, Jul 17, 2019 at 10:49 PM Christoph Hellwig <hch@....de> wrote:
>
> Hi Dan,
>
> was there any really good reason to have memremap.c in kernel/ back
> when you started it?  It seems to be pretty much tried into the mm
> infrastructure, and I keep mistyping the path.  Would you mind a simple
> git-mv patch after -rc1 to move it to mm/ ?

No complaints from me. It ended up there because it was originally
just the common memremap implementation always built with
CONFIG_HAS_IOMEM.

Arguably we should have done this move right after commit 5981690ddb8f
("memremap: split devm_memremap_pages() and memremap()
infrastructure").