From: "Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: cifs unable to access shares with read restricted at root level (bso#8950)
Date: Mon, 26 Oct 2015 13:18:17 +0100 [thread overview]
Message-ID: <20151026131817.3a8a3ded@aaptelpc> (raw)
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
Hi!
I've recently started working on bso#8950 [1] but I'm both a
kernel/SMB protocol newbie so bear with me... :-)
Shirish Pargaonkar provided a fix but it doesn't work on my setup. I
would like to provide a fix for SUSE even if temporary/hacky. Shirish's
approach seems sound so I've tried debugging it. I've summarized the
situation and my comments here [2].
There are a few things I don't understand yet.
* Where are disconnected dentries stored?
* How do you allocate a new dentry?
* What do d_obtain_alias() and d_splice_dentry() actually do? I've read
the doc strings several times but I still have a hard time wrapping my
head around it.
The result I'm getting seems to indicate that when an intermediary path
element is inaccessible an alternate root dentry directly pointing to
the requested path is created. The problem is that the prefixpath of
that is not stored anywhere so when we ask for a pattern to list the
content of that share, we use the path of the dentry from the root
(which is, well /) instead of the share prefixpath.
1: https://bugzilla.samba.org/show_bug.cgi?id=8950
2: http://diobla.info/doc/suse-todo#bnc799133
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG
Nürnberg)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2015-10-26 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 12:18 Aurélien Aptel [this message]
2015-10-26 12:54 ` cifs unable to access shares with read restricted at root level (bso#8950) Aurélien Aptel
2015-10-27 3:04 ` Shirish Pargaonkar
[not found] ` <CADT32eJgrjigh_ezCAJK-ivO-t_yygPEhgwoHKsE-8EdVxKP+Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-27 9:59 ` Aurélien Aptel
2015-10-28 0:43 ` Shirish Pargaonkar
[not found] ` <CADT32eJrSGmKW4ksKMNKS1KAYDcN8UxLGPLfm8+Ag9mCxkNdYA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-29 10:59 ` Aurélien Aptel
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=20151026131817.3a8a3ded@aaptelpc \
--to=aaptel-ibi9rg/b67k@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox