From: Miklos Szeredi <miklos@szeredi.hu>
To: Stef Bon <stefbon@gmail.com>
Cc: "fuse-devel@lists.sourceforge.net"
<fuse-devel@lists.sourceforge.net>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [fuse-devel] Changes in 4.7.
Date: Tue, 31 May 2016 09:17:56 +0200 [thread overview]
Message-ID: <CAJfpegveErYS8+23eNejT8K9Gimtw9w2kXRpyqhqQVSwCFBHgg@mail.gmail.com> (raw)
In-Reply-To: <CANXojcwuLVpyqkXxcUhKdG=nDEp-XspR4PtDerpoqO2FmMLp5w@mail.gmail.com>
On Tue, May 31, 2016 at 9:08 AM, Stef Bon <stefbon@gmail.com> wrote:
> Hi,
>
> I've read some news about the 4.7 kernel :
>
> "And in particular, if
> you're a low-level filesystem person, or involved in other ways in
> path component lookup (security layer etc), go check that everything
> looks ok, and if your filesystem isn't one that does parallel lookups
> or readdirs yet (because locking issues), take a look at that too."
>
> https://lkml.org/lkml/2016/5/29/77
>
> Does this have consequenses for fuse?
> I know that with some filesystems I've written the readdir call locks
> the directory exclusive.
The problem would be if the fuse filesystem assumed serialized
lookup/readdir and they don't do any locking themselves.
We probably need to conditionally re-add the lookup/readdir
serialization to the fuse kernel module, with an INIT flag to
explicitly enable parallel readdir and lookup (i.e. disable the
serialization).
Thanks,
Miklos
next parent reply other threads:[~2016-05-31 7:17 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 ` Miklos Szeredi [this message]
2016-05-31 10:57 ` [fuse-devel] Changes in 4.7 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
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=CAJfpegveErYS8+23eNejT8K9Gimtw9w2kXRpyqhqQVSwCFBHgg@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefbon@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 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).