From: Robin <beanow-1RVBLsOYap9hl2p70BpVqQ@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [4.13] Bad error message, old SMB protocol host.
Date: Tue, 15 Aug 2017 11:11:38 +0200 [thread overview]
Message-ID: <d236d2ff-da83-efce-51a3-d480e140ecf2@oscp.info> (raw)
When trying to mount an older SMB host share, the errors cifs produces
are very cryptic. Such as
CIFS VFS: cifs_mount failed w/return code = -112
Or
mount: mount //192.168.1.123/path/ on /mnt/path failed: Host is down
I reported this issue as a regression at first.
https://bugzilla.kernel.org/show_bug.cgi?id=196599
Thinking that cifs was just plain broken in this kernel as gvfs mounted
the same share just fine.
Can this protocol mismatch scenario have it's own, more informative
error message?
As this will likely effect more people when this change reaches the bulk
of users.
reply other threads:[~2017-08-15 9:11 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=d236d2ff-da83-efce-51a3-d480e140ecf2@oscp.info \
--to=beanow-1rvblsoyap9hl2p70bpvqq@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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