All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kjell Braden <afflux-7cISTWZqsW8RLla1DLYS2Q@public.gmane.org>
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] cifs: ensure that cifs_get_root() only traverses directories
Date: Sun, 03 Feb 2013 17:54:06 +0100	[thread overview]
Message-ID: <510E962E.5090103@pentabarf.de> (raw)
In-Reply-To: <510E9522.8040508-7cISTWZqsW8RLla1DLYS2Q@public.gmane.org>

On 2013-02-03 17:49, Kjell Braden wrote:
>    let me add that mounting paths below symlinks worked with the old path
> walking before commit fec11dd9a0109fe52fd631e5c510778d6cbff6cc.

Sorry, forgot specifics:

Consider the following tree:

   /srv/symtest
   /srv/symtest/dir
   /srv/symtest/dir/subdir/
   /srv/symtest/link -> dir/
   /srv/symtest/abslink -> /

this works:
    # mount.cifs //smbsrv/symtest/dir/subdir/ /mnt/

this causes oops but worked before fec11dd9a0:
    # mount.cifs //smbsrv/symtest/link/subdir/ /mnt/

this fails with ENOTDIR, both before fec11dd9a0 and after:
    # mount.cifs //smbsrv/symtest/abslink/srv/symtest/dir/subdir/ /mnt/

      parent reply	other threads:[~2013-02-03 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 20:11 [PATCH] cifs: ensure that cifs_get_root() only traverses directories Jeff Layton
     [not found] ` <1359749461-13458-1-git-send-email-jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-02-02  5:33   ` Steve French
2013-02-03 16:49   ` Kjell Braden
     [not found]     ` <510E9522.8040508-7cISTWZqsW8RLla1DLYS2Q@public.gmane.org>
2013-02-03 16:54       ` Kjell Braden [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=510E962E.5090103@pentabarf.de \
    --to=afflux-7cistwzqsw8rlla1dlys2q@public.gmane.org \
    --cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=smfrench-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 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.