From: "Steve French" <smfrench@gmail.com>
To: "Jeff Layton" <jlayton@redhat.com>
Cc: "Martin Koegler" <mkoegler@auto.tuwien.ac.at>,
linux-cifs-client@lists.samba.org, sfrench@samba.org,
niallain@gmail.com, linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] CIFS: Add nodfs mount option
Date: Thu, 16 Oct 2008 08:41:40 -0500 [thread overview]
Message-ID: <524f69650810160641q37ce109ft68d1e8e1031819dc@mail.gmail.com> (raw)
In-Reply-To: <20081016074305.306b2e90@barsoom.rdu.redhat.com>
Sounds reasonable to me - I will queue it up or something similar
unless there are any objections.
On Thu, Oct 16, 2008 at 6:43 AM, Jeff Layton <jlayton@redhat.com> wrote:
> On Thu, 16 Oct 2008 08:17:43 +0200
> Martin Koegler <mkoegler@auto.tuwien.ac.at> wrote:
>
>> Older samba server (eg. 3.0.24 from Debian etch) don't work correctly,
>> if DFS paths are used. Such server claim that they support DFS, but fail
>> to process some requests with DFS paths. Starting with Linux 2.6.26,
>> the cifs clients starts sending DFS paths in such situations, rendering
>> it unuseable with older samba servers.
>>
>> The nodfs mount options forces a share to be used with non DFS paths,
>> even if the server claims, that it supports it.
>>
>> Signed-off-by: Martin Koegler <mkoegler@auto.tuwien.ac.at>
>> ---
>>
>> This patch makes my home directory on a samba server useable for Linux 2.6.26
>> again. It still needs more testing. Should apply to linux 2.6.27 too.
>>
>> Would it be possible to support something like this in the offical CIFS client?
>>
>> diff a/fs/cifs/connect.c b/fs/cifs/connect.c
>> --- a/fs/cifs/connect.c
>> +++ b/fs/cifs/connect.c
>> @@ -90,6 +90,7 @@ struct smb_vol {
>> bool nocase:1; /* request case insensitive filenames */
>> bool nobrl:1; /* disable sending byte range locks to srv */
>> bool seal:1; /* request transport encryption on share */
>> + bool nodfs:1;
>> unsigned int rsize;
>> unsigned int wsize;
>> unsigned int sockopt;
>> @@ -1223,6 +1224,8 @@ cifs_parse_mount_options(char *options,
>> vol->sfu_emul = 1;
>> } else if (strnicmp(data, "nosfu", 5) == 0) {
>> vol->sfu_emul = 0;
>> + } else if (strnicmp(data, "nodfs", 5) == 0) {
>> + vol->nodfs = 1;
>> } else if (strnicmp(data, "posixpaths", 10) == 0) {
>> vol->posix_paths = 1;
>> } else if (strnicmp(data, "noposixpaths", 12) == 0) {
>> @@ -2167,6 +2170,10 @@ cifs_mount(struct super_block *sb, struc
>> volume_info.UNC,
>> tcon, cifs_sb->local_nls);
>> cFYI(1, ("CIFS Tcon rc = %d", rc));
>> + if (volume_info.nodfs) {
>> + tcon->Flags &= ~SMB_SHARE_IS_IN_DFS;
>> + cFYI(1, ("CIFS DFS disabeld (%d)", tcon->Flags));
>> + }
>> }
>> if (!rc) {
>> atomic_inc(&pSesInfo->inUse);
>> --
>
>
> Looks reasonable to me. Igor did most of the DFS work, so I cc'ed him
> here. Igor, any thoughts?
>
> --
> Jeff Layton <jlayton@redhat.com>
>
--
Thanks,
Steve
parent reply other threads:[~2008-10-16 13:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20081016074305.306b2e90@barsoom.rdu.redhat.com>]
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=524f69650810160641q37ce109ft68d1e8e1031819dc@mail.gmail.com \
--to=smfrench@gmail.com \
--cc=jlayton@redhat.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mkoegler@auto.tuwien.ac.at \
--cc=niallain@gmail.com \
--cc=sfrench@samba.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;
as well as URLs for NNTP newsgroup(s).