From: "J. Bruce Fields" <bfields@fieldses.org>
To: Neil Brown <neil@brown.name>
Cc: Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
lkml <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCHv2] Documentation: add new description of path-name lookup.
Date: Tue, 27 Oct 2015 17:21:45 -0400 [thread overview]
Message-ID: <20151027212145.GF14022@fieldses.org> (raw)
In-Reply-To: <87eggidtmd.fsf@notabene.neil.brown.name>
On Mon, Oct 26, 2015 at 03:35:54PM +0900, Neil Brown wrote:
> From c38784b876a181eda9a5687e618749157dc96a0e Mon Sep 17 00:00:00 2001
> From: NeilBrown <neil@brown.name>
> Date: Sat, 25 Jul 2015 10:24:41 +1000
> Subject: [PATCH] Documentation: add new description of path-name lookup.
>
> This document is based on three recent lwn.net articles.
> Some of the introductory material and linkage between articles
> has been removed, and some time-based descriptions have been
> revised.
Thanks for doing this! Nit:
> +End of the road
> +---------------
> +
> +Despite its complexity, all this pathname lookup code appears to be
> +in good shape - various parts are certainly easier to understand now
> +than even a couple of releases ago. But that doesn't mean it is
> +"finished". As already mentioned, RCU-walk currently only follows
> +symlinks that are stored in the inode so, while it handles many ext4
> +symlinks, it doesn't help with NFS, XFS, or Btrfs. That support
> +is not likely to be long delayed.
This looks likely to go stale quickly. Maybe just drop it?
I'd personally also probably drop the introduction. (I think of
Documetation/ as reference material with less of a need to tell a
"story".) But, I could be wrong.
--b.
next prev parent reply other threads:[~2015-10-27 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 0:28 [PATCH] Documentation: add new description of path-name lookup NeilBrown
2015-07-27 3:41 ` Randy Dunlap
2015-08-06 2:54 ` NeilBrown
2015-08-06 2:56 ` Randy Dunlap
2015-08-06 10:01 ` Jonathan Corbet
2015-10-26 6:35 ` [PATCHv2] " Neil Brown
2015-10-27 21:21 ` J. Bruce Fields [this message]
2015-10-27 23:12 ` Neil Brown
2015-11-03 1:19 ` Jonathan Corbet
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=20151027212145.GF14022@fieldses.org \
--to=bfields@fieldses.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
--cc=rdunlap@infradead.org \
--cc=viro@ZenIV.linux.org.uk \
/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.