From: "Steve French" <smfrench@gmail.com>
To: "Q (Igor Mammedov)" <niallain@gmail.com>
Cc: "Marcin Slusarz" <marcin.slusarz@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Steve French" <sfrench@samba.org>,
linux-cifs-client@lists.samba.org, stable@kernel.org
Subject: Re: [linux-cifs-client] [PATCH] cifs: fix oops on mount when CONFIG_CIFS_DFS_UPCALL is enabled
Date: Sun, 8 Jun 2008 15:16:38 -0500 [thread overview]
Message-ID: <524f69650806081316q219271e1qf33034a2a5463b28@mail.gmail.com> (raw)
In-Reply-To: <71bff3710806080428n18c8e56dwcda54c5c9460d265@mail.gmail.com>
I have not tried this code path recently and mount.cifs should always
be filling in the data field (with at least one mount option) but in a
case where the mount helper is missing, and the UNC name is of the
form //ip_address_of_server/share_name then I would prefer that we
treat this case (no mount options specified) as:
1) userid is \0 (null user)
2) null password
3) server id address comes from the beginning of the UNC name
(required or we fail)
The rest of the parms are at their defaults:
e.g. sec=ntlm (for smb2 this will be ntlmv2, and perhaps we should
change the default for cifs as well)
On Sun, Jun 8, 2008 at 6:28 AM, Q (Igor Mammedov) <niallain@gmail.com> wrote:
> A quick look trough cifs_mount and cifs_parse_mount_options functions shows
> that mount will fail anyway with error EINVAL when 'data' = NULL.
> May be moving NULL check at the beginning of function will be better
> in this case.
>
--
Thanks,
Steve
prev parent reply other threads:[~2008-06-08 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 19:00 Marcin Slusarz
2008-06-08 11:28 ` [linux-cifs-client] " Q (Igor Mammedov)
2008-06-08 20:16 ` Steve French [this message]
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=524f69650806081316q219271e1qf33034a2a5463b28@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=niallain@gmail.com \
--cc=sfrench@samba.org \
--cc=stable@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®