All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] [CIFS] ls on mounts to WindowsCE failing with invalid level message
Date: Wed, 24 Aug 2011 14:15:05 -0500	[thread overview]
Message-ID: <CAH2r5mtMNGTPHhCpfZAL3tjpsisxBejzwMJcSd8wLd4qLQbtWA@mail.gmail.com> (raw)
In-Reply-To: <20110824150852.5a9f911f-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>

Will fix the style comment - but on the fall back to lowest common
denominator ... it won't work.
For this server you have to fall back to 260 (then old servers fall
back to 1).  Interestingly this server seemed to have problems with
the default level and with level 1 ... so I don't see a choice to
having two fall backs (but could remove one of the three obviously).

On Wed, Aug 24, 2011 at 2:08 PM, Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> On Tue, 23 Aug 2011 22:16:54 -0500
> Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>> From 9b7b518633fd3187c7efe260fe20a0961e4a5f0b Mon Sep 17 00:00:00 2001
>> From: Steve French <sfrench-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
>> Date: Tue, 23 Aug 2011 22:00:26 -0500
>> Subject: [CIFS] ls on mounts to WindowsCE failing with invalid level message
>>
>> Mount succeeds to WindowsCE but when user tries
>> to access the contents of the directory gets "NT Status:
>> STATUS_INVALID_LEVEL" according to wireshark.
>>
>> This server does not support the common windows
>> readdir (Findfirst) level 257 nor level 258, so "fall back"
>> to level 260 if get an EOPNOTSUPP on level FIND_FILE_DIRECTORY_INFO
>> and while we are at it fall back to level 1 (FILE_INFO_STANDARD)
>> for very old servers if we get an EOPNOTSUPP on level 260.
>> (Note that the server returned errors on queries for inode
>> numbers via QueryPathInfo so we don't use the infolevel
>> SMB_FIND_FILE_ID_FULL_DIR_INFO)
>>
>> Reported-and-tested-by: Bryan James <Bryan.James.Krone-EXT-zES+1Ur7hjI@public.gmane.org>
>> Signed-off-by: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> ---
>>  fs/cifs/readdir.c |   17 +++++++++++++++++
>>  1 files changed, 17 insertions(+), 0 deletions(-)
>>
>> diff --git a/fs/cifs/readdir.c b/fs/cifs/readdir.c
>> index 5de03ec..ed29706 100644
>> --- a/fs/cifs/readdir.c
>> +++ b/fs/cifs/readdir.c
>> @@ -270,6 +270,7 @@ ffirst_retry:
>>               cifsFile->srch_inf.info_level = SMB_FIND_FILE_DIRECTORY_INFO;
>>       }
>>
>> +ffirst_retry_with_std_level:
>>       rc = CIFSFindFirst(xid, pTcon, full_path, cifs_sb->local_nls,
>>               &cifsFile->netfid, &cifsFile->srch_inf,
>>               cifs_sb->mnt_cifs_flags &
>> @@ -283,7 +284,23 @@ ffirst_retry:
>>               (cifs_sb->mnt_cifs_flags & CIFS_MOUNT_SERVER_INUM)) {
>>               cifs_sb->mnt_cifs_flags &= ~CIFS_MOUNT_SERVER_INUM;
>>               goto ffirst_retry;
>> +     } else if ((rc == -EOPNOTSUPP) && (cifsFile->srch_inf.info_level ==
>> +                                     SMB_FIND_FILE_DIRECTORY_INFO)) {
>
>                ^^^^ there's no need for the extra sets of parenthesis
>                here. That violates kernel coding conventions and makes this
>                harder to read.
>
>> +             /* Windows CE can return EOPNOTSUPP on FILE_DIRECTORY_INFO */
>> +             cifsFile->srch_inf.info_level =
>> +                             SMB_FIND_FILE_BOTH_DIRECTORY_INFO;
>                                ^^^^
>                        The code doesn't currently use
>                        BOTH_DIRECTORY_INFO anywhere. Would it be
>                        better to skip this step?
>
>> +             goto ffirst_retry_with_std_level;
>> +     } else if ((rc == -EOPNOTSUPP) && (cifsFile->srch_inf.info_level ==
>> +                                     SMB_FIND_FILE_BOTH_DIRECTORY_INFO)) {
>> +             cifsFile->srch_inf.info_level =
>> +                             SMB_FIND_FILE_FULL_DIRECTORY_INFO;
>
>                                ^^^^
>                        Ditto here. Would it be best to just fall back
>                        to the lowest common denominator here? I'm not sure
>                        I see a lot of benefit in using any of these
>                        other infolevels. We'll basically get the same
>                        info out of SMB_FIND_FILE_INFO_STANDARD and it's
>                        more widely supported.
>
>> +             goto ffirst_retry_with_std_level;
>> +     } else if ((rc == -EOPNOTSUPP) && (cifsFile->srch_inf.info_level ==
>> +                                     SMB_FIND_FILE_FULL_DIRECTORY_INFO)) {
>> +             cifsFile->srch_inf.info_level = SMB_FIND_FILE_INFO_STANDARD;
>> +             goto ffirst_retry_with_std_level;
>>       }
>> +
>>  error_exit:
>>       kfree(full_path);
>>       cifs_put_tlink(tlink);
>
>
> --
> Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
>



-- 
Thanks,

Steve

      parent reply	other threads:[~2011-08-24 19:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  3:16 [PATCH] [CIFS] ls on mounts to WindowsCE failing with invalid level message Steve French
     [not found] ` <CAH2r5mvmVNySCiSMc9Bz=yi4Zhzg=sYwxLSpiwapAyn6-HEqDQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-08-24 19:08   ` Jeff Layton
     [not found]     ` <20110824150852.5a9f911f-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2011-08-24 19:15       ` 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=CAH2r5mtMNGTPHhCpfZAL3tjpsisxBejzwMJcSd8wLd4qLQbtWA@mail.gmail.com \
    --to=smfrench-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.