linux-kernel - Re: [PATCH 1/3] generic sys_old

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>] [day] [month] [year] [list]

Message-ID: <20100108225231.GA11332@rhlx01.hs-esslingen.de>
Date:	Fri, 8 Jan 2010 23:52:31 +0100
From:	Andreas Mohr <andi@...as.de>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Christoph Hellwig <hch@....de>, Al Viro <viro@...IV.linux.org.uk>,
	Matthew Wilcox <matthew@....cx>, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
	linux@....linux.org.uk, dhowells@...hat.com,
	ysato@...rs.sourceforge.jp, tony.luck@...el.com
Subject: Re: [PATCH 1/3] generic sys_old_select

> There is, however, a reason *not* to do it which should be carefully
> considered: by co-locating the compatibility version with the modern
> version, it gets access to static functions that are part of the
> implementation of the modern version.  If we move the compatibility
> versions out, it may entail having to export those statics.
> 
>         -hpa

Hmm, do I hear a reason to simply fully #include the (newly separated)
old-style .c file from within the new-style .c file?
Not necessarily a wonderful approach, but perhaps it beats doing a "correct
full separation" and thus having a couple new-born (and unhappy ;) exports
any day?

Andreas Mohr
--
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/