linux-kernel - Re: [Tux3] Tux3 report: Tux3 Git tree available

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: <200903121424.08961.phillips@phunq.net>
Date:	Thu, 12 Mar 2009 14:24:08 -0700
From:	Daniel Phillips <phillips@...nq.net>
To:	tux3@...3.org
Cc:	Andi Kleen <andi@...stfloor.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [Tux3] Tux3 report: Tux3 Git tree available

On Thursday 12 March 2009, Andi Kleen wrote:
> to be honest the estimate of adding btree directories in 3kLOC
> of code seems very optimistic.

Is that a bet?

> >> This symbol is only supposed to be shared between separate compilation
> >> units within fs/tux3, not be visible outside our module.  How do we do
> >> that?
> >
> > You can't.  Bear in mind that we want the allyesconfig kernel to link
> > and run, and that includes tux3.  So do it manually by prefixing
> > everything with tux3_ or whatever.  (does it need the "3"?)
> 
> AFAIK it could be done by using special linker scripts for the sublinks.
> But I'm not sure it's worth it because that would require listing of the symbols
> in some file. Would need some Makefile magic.
> 
> For modules I also had the "namespace" patches some time ago which implemented
> simple namespace support. Should probably resurrect that.

Per-module name scope would be a nice creature comfort.  Well, for now
the offending names will just get tux_ed.

Regards,

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