linux-kernel - Re: [PATCH v2] mm: cleaning per architecture MM hook header files

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]

Message-Id: <20150709160934.888dad2b24ce45957e65b139@linux-foundation.org>
Date:	Thu, 9 Jul 2015 16:09:34 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Laurent Dufour <ldufour@...ux.vnet.ibm.com>
Cc:	Vineet Gupta <Vineet.Gupta1@...opsys.com>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	uclinux-h8-devel@...ts.sourceforge.jp, linux-arch@...r.kernel.org,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	Oleg Nesterov <oleg@...hat.com>
Subject: Re: [PATCH v2] mm: cleaning per architecture MM hook header files

On Wed,  1 Jul 2015 12:17:33 +0200 Laurent Dufour <ldufour@...ux.vnet.ibm.com> wrote:

> The commit 2ae416b142b6 ("mm: new mm hook framework") introduced an empty
> header file (mm-arch-hooks.h) for every architecture, even those which
> doesn't need to define mm hooks.
> 
> As suggested by Geert Uytterhoeven, this could be cleaned through the use
> of a generic header file included via each per architecture
> asm/include/Kbuild file.
> 
> The PowerPC architecture is not impacted here since this architecture has
> to defined the arch_remap MM hook.

So the way this works is that if an arch wants to override a hook, it
will remove the "generic-y += mm-arch-hooks.h" and add
arch/XXX/include/asm/mm-arch-hooks.h, yes?

And the new arch/XXX/include/asm/mm-arch-hooks.h only needs to define
the hook(s) which the arch wants to override?

So nothing will ever be added to include/asm-generic/mm-arch-hooks.h?

Seems fair enough.

Oleg is angling to remove arch_remap(), so there won't be anything left
in these files!  But there are plenty of ad-hoc things which *should*
be moved over.

> Changes in V2:
> --------------
>  - Vineet Gupta reported that the Kbuild files should be kept sorted.

Yes, we do this to avoid patch collisions.  Everyone always adds stuff
to the end of the list (Makefiles, #includes, etc etc), thus carefully
maximizing the number of patch collisions :(

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/