| 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
| ||
|
Date: Mon, 12 Jan 2009 13:23:07 -0600 From: "Steve French" <smfrench@...il.com> To: "Greg KH" <gregkh@...e.de> Cc: "Randy Dunlap" <randy.dunlap@...cle.com>, "Stephen Rothwell" <sfr@...b.auug.org.au>, linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, sfrench@...ba.org Subject: Re: linux-next: Tree for January 12 (cifs vs. staging) Is there some magic compile option alternative (other than renaming the function, which may be ok, since others probably don't depend on it)? MD5Init is used outside fs/cifs/md5.c so can't be static On Mon, Jan 12, 2009 at 1:13 PM, Greg KH <gregkh@...e.de> wrote: > On Mon, Jan 12, 2009 at 12:58:42PM -0600, Steve French wrote: >> There is not just the cifs md5 one (which has been around a long >> time), but an md5_init (static) in crypto and the new one in rt. The >> addition of the new one (rt md5_init) causes the build problem. It >> would be nice if we could use the same md5 routines though ... last >> time we checked the crypto one was not well suited for calculating >> signatures as a network fs would do though. > > I'll fix up the staging rt drivers to not do this, but cifs shouldn't be > declaring such functions as globals either :) > > thanks, > > greg k-h > -- Thanks, Steve -- 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