| 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: Wed, 9 Sep 2009 13:20:39 -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 Wed, 9 Sep 2009 13:07:52 -0400 (EDT) Christoph Lameter <cl@...ux-foundation.org> wrote: > On Wed, 9 Sep 2009, Jeff Layton wrote: > > > My suspicion would be that the server needs to perform an oplock break > > to another client before it can send the response. The only way I know > > how to tell that is to sniff all SMB traffic on the server and watch > > for oplock break calls to other clients when these stalls occur. > > That could be tested by switching them off right? If I do > > echo 0 >/proc/fs/cifs/OplockEnabled > > and then remount the volume it should switch off oplocks? > > This has no effect on the stalls. > That'll stop your client from requesting oplocks, but that won't prevent others from doing so. If my suspicion is correct, then another client is holding an oplock and the server needs to break it before it can reply to yours. Unfortunately I doubt there's much you can do from your client to prevent that (if that is the case). There may be a way to turn off oplocks on the server side, but that may very well be even worse for performance. -- 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/
Powered by blists - more mailing lists