2011/8/26 Pavel Shilovsky <piastryyy@xxxxxxxxx>: > 2011/8/22 Rafael Ganascim <rganascim@xxxxxxxxx>: >> Hi, >> >> I think that this problem is related to: >> >> http://article.gmane.org/gmane.linux.kernel.cifs/3878 >> >> >> I have this fileserver structure: >> - complete path: //fileserver-la-01/ti$/geral/ >> - //fileserver-la-01/ti$: in this parent dir, my user don't have >> permission to access >> >> >> Using the kernel version 2.6.38 the mount reports: >> >> # mount -v /mnt/xxxx/latigeral/ >> parsing options: rw,credentials=/etc/credentials,uid=1000 >> >> mount.cifs kernel mount options >> unc=//fileserver-la-01\ti$,user=xxxxxx,pass=xxxxx,ver=1,rw,credentials=/etc/credentials,uid=1000,prefixpath=geral/ >> # >> >> >> Using the kernel 3.0.2: >> >> # mount -v /mnt/xxxx/latigeral >> parsing options: rw,credentials=/etc/credentials,uid=1000 >> >> mount.cifs kernel mount options >> unc=//fileserver-la-01\ti$,user=xxxxxx,pass=xxxxx,ver=1,rw,credentials=/etc/credentials,uid=1000,prefixpath=geral/ >> mount error(13): Permission denied >> Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) >> # >> >> The cifsFYI messages are in the attachments, cifsFYI.txt. >> >> To workaround this problem (in my box), I had set the 'full_path' >> (from prefixpath) in the call to cifs_get_inode_info in the function >> cifs_root_iget (~ inode.c:888), if the prefixpath isn't null. This >> worked for me, but it's bad solution, I think (i'm not a programmer :( >> ). >> >> What do you think about this problem? There are a 'good' solution for it? >> >> >> Thanks, >> -- >> >> Rafael Ganascim >> > > Hi! > > I posted the patch "CIFS: Fix NT_STATUS_ACCESS for moutn with > prefixpath option" to the list - that should help. > > Jeff, Al, can you comment on this, please? > > -- > Best regards, > Pavel Shilovsky. > Sorry - wrong title. resend as "CIFS: Fix NT_STATUS_ACCESS_DENIED for mounts with prefixpath option" patch. -- Best regards, Pavel Shilovsky. -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
