From: Stef Bon <stefbon@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: "fuse-devel@lists.sourceforge.net"
<fuse-devel@lists.sourceforge.net>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [fuse-devel] Changes in 4.7.
Date: Wed, 1 Jun 2016 16:44:40 +0200 [thread overview]
Message-ID: <CANXojcw8pJDa66YS+0T-TjetmRwPgfdXWbNzi8rkUv6WKzUydQ@mail.gmail.com> (raw)
In-Reply-To: <20160601135209.GG14480@ZenIV.linux.org.uk>
2016-06-01 15:52 GMT+02:00 Al Viro <viro@zeniv.linux.org.uk>:
> For regular files, the kernel serializes read()/write()/lseek() done on
> descriptors aliasing each other. Now it does the same for getdents()/lseek()
> of directories.
>
> From the filesystem point of view, you might see two getdents() called
> in parallel only if their results should be unaffected by the order of
> operations.
Ah right! Now I understand. Thanks a lot for your explanation!
Of course when a second descriptor refers the same object, operations
like read/lseek have to be serialized.
If not strange things will happen.
I was thinking on a totally different level.
Stef
prev parent reply other threads:[~2016-06-01 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANXojcwuLVpyqkXxcUhKdG=nDEp-XspR4PtDerpoqO2FmMLp5w@mail.gmail.com>
2016-05-31 7:17 ` [fuse-devel] Changes in 4.7 Miklos Szeredi
2016-05-31 10:57 ` Stef Bon
2016-05-31 11:09 ` Miklos Szeredi
[not found] ` <nijg09$6k0$1@ger.gmane.org>
[not found] ` <CAJfpegvJoSK6fQEGWj_uEQF8q2jYmdqUyKy1-m5DxFMUFc0rEg@mail.gmail.com>
[not found] ` <CAJfpeguV3H_oC=5FM3G8tVsrY7Fiy2LX0JKttFBGQWN+SC6_YQ@mail.gmail.com>
[not found] ` <87shwy8b38.fsf@thinkpad.rath.org>
2016-05-31 16:25 ` Stef Bon
2016-05-31 17:22 ` Stef Bon
2016-05-31 17:44 ` Al Viro
2016-05-31 18:44 ` Stef Bon
2016-05-31 20:29 ` Al Viro
2016-06-01 12:32 ` Stef Bon
2016-06-01 13:52 ` Al Viro
2016-06-01 14:44 ` Stef Bon [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=CANXojcw8pJDa66YS+0T-TjetmRwPgfdXWbNzi8rkUv6WKzUydQ@mail.gmail.com \
--to=stefbon@gmail.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.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 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).