mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kyle Davenport <kdd@tvmax.net>
To: linux-kernel@vger.kernel.org
Subject: linux 2.4.25 crashes windows
Date: Sun, 04 Apr 2004 12:03:11 -0500	[thread overview]
Message-ID: <1081098190.14744.90.camel@quickest.kyledavenport.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

No joke.  64-bit Windows Advanced Server 2003 blue-screens on file share
access.  I was using Samba 3.0 on RH8 to routinely access windows
shares.  When I upgraded from 2.4.22 to 2.4.25, any attempt to access a
sub-directory of a share mounted from 64-bit Win2003, immediately
crashes windows.  I rolled back to 2.4.22 and no crash.  I tried 2.4.25
against a 32-bit 2003 Win2003, and no crash.  I didn't test different
versions of Samba.  But on 2.4.25, trying to ls a sub-directory of the
mounted share or cd to that sub-directory, instantly and repeatedly
blue-screens windows.  

I have no idea how the kernel change could be causing this.  Seems to me
like it should depend entirely on Samba.  I did attempt to reproduce the
problem with tcp-replay.  I sent the identical tcp/ip packets involved
without crashing windows.  Apparently share authentication is required.

My company has informed Microsoft of the problem, weeks ago, but I am
getting tired of waiting for a fix.

Congrats to everyone involved!


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-04-04 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-04 17:03 Kyle Davenport [this message]
2004-04-04 19:46 ` Urban Widmark
2004-04-05  4:57   ` Kyle Davenport
2004-04-22 17:34     ` Urban Widmark

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1081098190.14744.90.camel@quickest.kyledavenport.com \
    --to=kdd@tvmax.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®