linux-kernel - Re: 2.6.31-rc8: CIFS with 5 seconds hiccups

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: <20090910201932.5b8356e2@tlielax.poochiereds.net>
Date:	Thu, 10 Sep 2009 20:19:32 -0400
From:	Jeff Layton <jlayton@...hat.com>
To:	Christoph Lameter <cl@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, samba@...ts.samba.org,
	linux-cifs-client@...ts.samba.org
Subject: Re: 2.6.31-rc8: CIFS with 5 seconds hiccups

On Thu, 10 Sep 2009 17:27:53 -0400 (EDT)
Christoph Lameter <cl@...ux-foundation.org> wrote:

> Right. 32 bit cannot mount the clameter directory for strange reasons. I
> have to go one level higher.
[...]
> One other issue that may be important: The mounting operation is very slow
> on 32 bit. Could it be that the handshake does not work out?

Ok, looks like the 64 bit client is using a different level of interest
than the 32 bit on the FIND_FIRST call. I suspect that that difference
may account for the difference in response time.

It's not completely clear to me why that would be. Maybe a windows bug
that causes a slowdown with that LOI?

In any case, I think we need to look closely at what's happening at
mount time. First, I'll need some other info:

1) output of "/sbin/mount.cifs -V" from both machines

2) mount options that you're using on both boxes

3) wire captures from mount attempts on both machines. Try to mount the
"clameter" dir on both boxes and do captures of each attempt. Maybe
this time use -s 0 with tcpdump so we get all of the traffic.

There may be crackable password hashes in the captures, so you may want
to send them to me privately and not cc the list.

Thanks,
-- 
Jeff Layton <jlayton@...hat.com>
--
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/