linux-kernel - Re: mounting cifs filesystems not possible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <524f69650907230044u5ab44c59y91bc9b808f5fd6c3@mail.gmail.com>
Date:	Thu, 23 Jul 2009 02:44:30 -0500
From:	Steve French <smfrench@...il.com>
To:	Gerhard Hintermayer <gerhard.hintermayer@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: mounting cifs filesystems not possible

On Thu, Jul 23, 2009 at 1:24 AM, Gerhard
Hintermayer<gerhard.hintermayer@...il.com> wrote:
> See my original post to LKML at http://lkml.org/lkml/2009/7/15/217.
> You can see kernel version, and dmesg output (including cifsFYI set to
> 7) there.
> I did file a bug report to gentoo bug list and lkml. Shall I also do
> so for bugzilla.samba.org ? I think it's more kernel related.
>
> The DebugData of the share I'm trying to mount (fortunaltely I got a

> mount -t cifs -o user=aprol,password=*****,ip=10.5.12.105 //BRKVN05/AtlasPM /mnt/AtlasPM

The mount syntax you listed in your post is a little strange with the
mount options preceding rather than following the UNC name and device,
ie rather than the usual:
              mount.cifs {//unc-name} {mount-point} [-o options]

It looks like the first 3/4 of mount succeeded (setting up a session,
and connecting to the share) to the point of doing the lookup of the
root directory of the share (which I don't see in your trace).
Typically there have been the following reasons for that to fail:
1) the user has no permission on the root of the share
or
2) the root of the share is a dfs referral to another server (this
should work now, but was probably not supported a few kernel releases
ago)
or
3) the server reports that the root directory is not a directory (ie
is a file for example)

It may be that an earlier mount failed perhaps oopsing in the vfs, and
that could have left an existing cifs session and tree connection
which made it seem like a later mount worked (since it found an
existing session) but that seems unlikely.

It would be helpful to see if the client did a network request (in
this case SMB transact2 Query Path Info) on the root directory of the
share, so if you have a wireshark trace that would be useful.
-- 
Thanks,

Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/