mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: kernel@cnspc18.murdoch.edu.au
Subject: [Bug 1853] New: smbfs reconnect does not quite work	properly
Date: Mon, 12 Jan 2004 22:51:10 -0800	[thread overview]
Message-ID: <901260000.1073976670@[10.10.2.4]> (raw)

http://bugme.osdl.org/show_bug.cgi?id=1853

           Summary: smbfs reconnect does not quite work properly
    Kernel Version: 2.6.1-rc3
            Status: NEW
          Severity: normal
             Owner: fs_samba-smb@kernel-bugs.osdl.org
         Submitter: kernel@cnspc18.murdoch.edu.au


Distribution: Debian testing/unstable 
Hardware Environment: PIII/450 
Software Environment:  
Problem Description: 
smbfs mount reconnection due to inactivity timeout should not pass failure 
back to userspace 
 
Steps to reproduce: 
* Mount remote smbfs drive (eg. from a Win98 or W2K box). 
* Wait for it to time out (eg. by not accessing it for a couple of hours). 
* Access the drive. 
    Under 2.4.x I would have seen message such as: 
      Jan 10 06:25:48 wibble kernel: smb_get_length: recv error = 5 
      Jan 10 06:25:48 wibble kernel: smb_request: result -5, setting invalid 
      Jan 10 06:25:48 wibble kernel: smb_retry: successful, new pid=31576, 
generation=43 
    The connection would immediately get reestablished and userspace would be 
none the wiser that anything went wrong. 
    Under 2.6.1-rc3 however: 
      Jan 12 02:01:28 wibble kernel: SMB connection re-established (-5) 
      Jan 12 02:01:28 wibble kernel: smb_lookup: find //Program Files failed, 
error=-57 
      And userspace would see an error: 
      find: /mnt/blue: Invalid slot 
    Subsequent accesses to the drive work fine. It would be infinitely 
preferable for the error not reach userspace.



                 reply	other threads:[~2004-01-13  6:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='901260000.1073976670@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=kernel@cnspc18.murdoch.edu.au \
    --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®