linux-kernel - Re: linux-next: Tree for January 12 (cifs vs. staging)

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: <20090112192351.GA7607@suse.de>
Date:	Mon, 12 Jan 2009 11:23:51 -0800
From:	Greg KH <gregkh@...e.de>
To:	Dave Kleikamp <shaggy@...ux.vnet.ibm.com>
Cc:	Steve French <smfrench@...il.com>,
	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)

On Mon, Jan 12, 2009 at 01:19:18PM -0600, Dave Kleikamp wrote:
> On Mon, 2009-01-12 at 12:58 -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.
> 
> Is that due to the byte-swapping?  Can the cifs and rt* drivers use the
> same code.  rt28[67]0/common/md5.c are identical files.  In fact those
> "common" directories should probably be combined into a single truly
> common directory.

Yes, the "common" directories are going to be merged, but as they
originally came from different driver sources, they didn't start out
that way.  It will take some refactoring to get it to work properly,
which is on my todo list...

thanks,

greg k-h
--
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/