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:	Thu, 30 Apr 2009 16:40:57 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Mel Gorman <mel@....ul.ie>
Cc:	Eric Lacombe <goretux@...il.com>, linux-kernel@...r.kernel.org,
	davej@...hat.com, tglx@...utronix.de
Subject: Re: [unused symbol] need to use init_mm


* Mel Gorman <mel@....ul.ie> wrote:

> On Thu, Apr 30, 2009 at 12:32:04PM +0200, Eric Lacombe wrote:
> > Hi,
> > 
> > Within a module I work on, I need to access to init_mm, but as it is marked 
> > UNUSED, I wonder if there is another way (an API) to access to it.
> > Otherwise, what can I do to have this mark removed from init_mm in the 
> > mainline? as my module is really not yet ready for inclusion.
> > 
> > Thanks in advance for your response,
> > 
> 
> It looks to be that it was removed already, somewhat behind schedule, in
> commit 9470565579f29486f4ed0ffa50774268b64994b0 after an initial attempt
> was made in commit 3abf024d2abb79614d8c4cb25a70d5596f77d0ad.  I don't know
> if there is a procedure for bringing it back but I would guess it's a call
> for the x86 maintainers. I imagine they will want to at least know;
> 
> 1. Why do you need init_mm exported?
> 2. Is there an alternative approach to using init_mm?
> 3. Assuming yes, what are the downsides?
> 4. When do you think the module will be ready for posting?  i.e. is this
>    really something destined for mainline or some perma-out-of-tree?

yes, those questions have to be answered.

	Ingo
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ