linux-kernel - Re: [PATCH 1/2] modules: add default loader hook implementations

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: <BANLkTi=6RkrRHeNtDhpebKx7cNXNKvbxtw@mail.gmail.com>
Date:	Thu, 30 Jun 2011 15:43:43 -0400
From:	Mike Frysinger <vapier.adi@...il.com>
To:	Jonas Bonn <jonas@...thpole.se>
Cc:	rusty@...tcorp.com.au, arnd@...nb.de, geert@...ux-m68k.org,
	mingo@...e.hu, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org, monstr@...str.eu, cmetcalf@...era.com,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org
Subject: Re: [PATCH 1/2] modules: add default loader hook implementations

On Thu, Jun 30, 2011 at 15:22, Jonas Bonn wrote:
> -/* These must be implemented by the specific architecture */
> +/* These may be implemented by architectures that need to hook into the
> + * module loader code.  Architectures that don't need to do anything special
> + * can just rely on the 'weak' default hooks defined in kernel/module.c.
> + * Note, however, that at least one of apply_relocate or apply_relocate_add
> + * must be implemented by each architecture.
> + */

still need to update this multi-line comment ;)
-mike
--
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/