[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081209212611.25fcd053@tupile.poochiereds.net>
Date: Tue, 9 Dec 2008 21:26:11 -0500
From: Jeff Layton <jlayton@...hat.com>
To: Dennis Hardy <dhardy@...etthis.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: CIFS regression in 2.6.27.8
On Tue, 9 Dec 2008 13:47:56 -0800 (PST)
Dennis Hardy <dhardy@...etthis.com> wrote:
>
> > I tried it on both i386 and x86_64 and had no problems. Is this client
> > non-x86 by any chance?
>
> Curious...my kernel is CONFIG_X86_32=y and CONFIG_X86=y, CONFIG_MK6=y.
>
> Perhaps this could be an issue with the Windows Server side (Windows Home
> Server, latest Windows SPs, etc.) Maybe MSFT introduced some "improvement"
> in a recent update that caused an incompatibility of some sort. I can try
> mounting some other Windows machines via CIFS from the 2.6.27.8 end and see
> what happens, plus boot back to 2.6.27.6 and compare.
>
There is a problem with CIFS in 2.6.27.8, but it mainly manifests
itself as a kthread that doesn't shut down when it should (regression
due to a missing couple of prerequisite patches). I've got a patch for
2.6.27.9 that should fix that problem (assuming there is a .9)
The fixes that went into 2.6.27.8 were mostly patches to fix races on
mount and unmount and some fixes for socket handling. The problem
you've described seems very consistent and localized to an area that
wasn't patched in .8.
I could easily be wrong, but the problem you've described seems more
likely to be a server issue. If you can get binary network captures
between the client and server like Steve F. requested, then we should
be able to confirm it either way...
--
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