From: "L. A. Walsh" <cifs@tlinx.org>
To: Steve French <smfrench@gmail.com>
Cc: L A Walsh <cifs@tlinx.org>, Pavel Shilovsky <piastryyy@gmail.com>,
linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: upcalls seem to have problems with symlinks, junctions et al.
Date: Fri, 22 Feb 2019 01:56:31 -0800 [thread overview]
Message-ID: <5C6FC74F.3020907@tlinx.org> (raw)
In-Reply-To: <CAH2r5mskDv3ZB8gUpRDN6iPzaZaGeXuN-uHikGvj+5K4epN2Xg@mail.gmail.com>
On 2/21/2019 8:30 PM, Steve French wrote:
> I have wanted to change this code and improve it for a while - one
> thing which is tricky is showing mode bits when no permissions to read
> permissions though, and we also need to clean up and simplify some of
> this code. Let's follow up on this in a few days, if you are
> flexible and can install some test patches
>
Usually links on linux have 777 permissions and aren't
changeable, though things are changing.
As for testing -- should be able, but maybe not
too fast.
Dunno if you rememeber, but I had some probs w/links back
around Feb 2-3 2017...and you asked for a wireshark
trace that I sent on on the 3rd...then we both got
distracted.
(same list)
I sometimes have a long cycle time...you too? :-)
I could send the dump again... ;-) Seriously, I went
back to using a single UID mount and that works around
the problem, as in my case I have perms to read all
of the links.
I just recently tried it again -- and hit the same
type of behavior.
next prev parent reply other threads:[~2019-02-22 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 5:51 regressions & flakiness make for ugly symlink links L A Walsh
2019-02-19 19:46 ` Pavel Shilovsky
2019-02-20 19:48 ` L A Walsh
2019-02-21 23:16 ` Re:upcalls seem to have problems with symlinks, junctions et al L A Walsh
2019-02-22 4:30 ` upcalls " Steve French
2019-02-22 9:56 ` L. A. Walsh [this message]
2019-02-22 20:31 ` L A Walsh
2019-02-27 8:54 ` L A Walsh
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=5C6FC74F.3020907@tlinx.org \
--to=cifs@tlinx.org \
--cc=linux-cifs@vger.kernel.org \
--cc=piastryyy@gmail.com \
--cc=smfrench@gmail.com \
/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.