From: Christoph Hellwig <hch@infradead.org>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: NeilBrown <neilb@suse.de>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Andreas Dilger <adilger@dilger.ca>
Subject: Re: For review: open_by_name_at(2) man page
Date: Tue, 18 Mar 2014 06:07:08 -0700 [thread overview]
Message-ID: <20140318130708.GA13031@infradead.org> (raw)
In-Reply-To: <53283D7A.1020409@gmail.com>
On Tue, Mar 18, 2014 at 01:35:06PM +0100, Michael Kerrisk (man-pages) wrote:
> Indeed! I don't know quite what I was smoking as I reviewed that piece.
> In fact, I started writing this page a long time ago, but then other
> events intervened, and it was a long time before I came back to it recently.
> Certainly, when I produced that shell session log, things proceeded
> (almost) as shown. I'm guessing that what happened is that I by
> accident edited out a line
>
> rm cecilia.txt
>
> just before
>
> echo 'Warum?' > cecilia.txt
>
> Fixed now. (In that case of course, it is of course a matter of chance
> whether the pathname is re-created with the same i-node number, but if
> you are quick, it often is. I'll add some explanation to the page.)
That's why the file handles contain a generation counter that gets
incremented in this case.
next prev parent reply other threads:[~2014-03-18 13:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 15:57 For review: open_by_name_at(2) man page Michael Kerrisk (man-pages)
2014-03-17 22:00 ` NeilBrown
2014-03-18 9:43 ` Christoph Hellwig
2014-03-18 12:37 ` Michael Kerrisk (man-pages)
[not found] ` <53283DFB.6040105-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-18 22:24 ` NeilBrown
2014-03-18 22:24 ` NeilBrown
2014-03-19 9:09 ` Michael Kerrisk (man-pages)
[not found] ` <20140318090007.3adee3d0-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2014-03-18 12:35 ` Michael Kerrisk (man-pages)
2014-03-18 12:35 ` Michael Kerrisk (man-pages)
2014-03-18 13:07 ` Christoph Hellwig [this message]
2014-03-18 13:30 ` Michael Kerrisk (man-pages)
2014-03-18 9:37 ` Christoph Hellwig
2014-03-18 12:41 ` Michael Kerrisk (man-pages)
2014-03-18 12:55 ` For review: open_by_name_at(2) man page [v2] Michael Kerrisk (man-pages)
[not found] ` <53284233.3050800-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-19 4:13 ` NeilBrown
2014-03-19 4:13 ` NeilBrown
[not found] ` <20140319151349.33a76023-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2014-03-19 9:09 ` Michael Kerrisk (man-pages)
2014-03-19 9:09 ` Michael Kerrisk (man-pages)
[not found] ` <53295ED0.7070304-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-19 14:14 ` For review: open_by_handle_at(2) man page [v3] Michael Kerrisk (man-pages)
2014-03-19 14:14 ` Michael Kerrisk (man-pages)
2014-03-19 6:42 ` For review: open_by_name_at(2) man page [v2] Mike Frysinger
2014-03-19 13:11 ` Michael Kerrisk (man-pages)
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=20140318130708.GA13031@infradead.org \
--to=hch@infradead.org \
--cc=adilger@dilger.ca \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=neilb@suse.de \
/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.