From: Roman Mamedov <rm@romanrm.net>
To: Filipe Manana <fdmanana@kernel.org>
Cc: Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, Fabian Vogt <fvogt@suse.com>
Subject: Re: [PATCH 2/2] btrfs: canonicalize the device path before adding it
Date: Tue, 24 Sep 2024 21:21:04 +0500 [thread overview]
Message-ID: <20240924212104.73963614@nvm> (raw)
In-Reply-To: <CAL3q7H7aL-M3dyu7f7w1bBb5zUP00KMp=F-jWV-Q0hZH6LD=yw@mail.gmail.com>
On Tue, 24 Sep 2024 13:12:09 +0100
Filipe Manana <fdmanana@kernel.org> wrote:
> > +/*
> > + * We can have very wide soft links passed in.
>
> Wide? Did you mean wild in the sense of unusual?
Samba uses this term to refer to links pointing outside of the particular
network share tree:
https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#WIDELINKS
https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html#ALLOWINSECUREWIDELINKS
Not sure what is the origin or etymology, guess it may stem from "VFS-wide",
links across the entire pathname space.
--
With respect,
Roman
next prev parent reply other threads:[~2024-09-24 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 5:17 [PATCH 0/2] btrfs: enhance btrfs device path rename Qu Wenruo
2024-09-24 5:17 ` [PATCH 1/2] btrfs: avoid unnecessary device path update for the same device Qu Wenruo
2024-09-24 11:47 ` Filipe Manana
2024-09-24 21:12 ` Qu Wenruo
2024-09-24 5:17 ` [PATCH 2/2] btrfs: canonicalize the device path before adding it Qu Wenruo
2024-09-24 12:12 ` Filipe Manana
2024-09-24 16:21 ` Roman Mamedov [this message]
2024-09-24 21:16 ` Qu Wenruo
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=20240924212104.73963614@nvm \
--to=rm@romanrm.net \
--cc=fdmanana@kernel.org \
--cc=fvogt@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).