Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>
To: Shirish Pargaonkar
	<shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: cifs unable to access shares with read restricted at root level (bso#8950)
Date: Tue, 27 Oct 2015 10:59:05 +0100	[thread overview]
Message-ID: <20151027105905.0644daf2@aaptelpc> (raw)
In-Reply-To: <CADT32eJgrjigh_ezCAJK-ivO-t_yygPEhgwoHKsE-8EdVxKP+Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]

Hi Shirish,

On Mon, 26 Oct 2015 22:04:28 -0500 Shirish Pargaonkar
<shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> They are stored in a linked list of struct cifs_rdelem off of
> superblock where each element of this linked list points to a
> disconnected dentry.

This list is only used use when we mount with noserverino. It doesn't
work in both case anyway.
 
> > * 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.
> 
> I think the simplistic answer is d_obtain_alias creates a dentry
> without a parent and d_splice_dentry connects a disconnected dentry
> to a parent. So let us say you have a a filesystem like /a/b/c/d/e/f
> where c is not accessible, we would create a disconnected for d (and
> for all the entries starting d such as e and f)
> Then when c is accessible and we are trying to reach f, while
> traversing, for each dentry we would look whether it is disconnected
> or not and if found (by any of three search routines), splice dentry
> with c.
> 
> What kind of setup do you have where the patchset is not working?

Everything is explained on the link I provided. It's the same setup you
used I think.

  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 --]

  parent reply	other threads:[~2015-10-27  9:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 12:18 cifs unable to access shares with read restricted at root level (bso#8950) Aurélien Aptel
2015-10-26 12:54 ` 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 [this message]
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=20151027105905.0644daf2@aaptelpc \
    --to=aaptel-ibi9rg/b67k@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@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