linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stef Bon <stefbon@gmail.com>
To: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Cc: "fuse-devel@lists.sourceforge.net" <fuse-devel@lists.sourceforge.net>
Subject: Re: [fuse-devel] Changes in 4.7.
Date: Tue, 31 May 2016 12:57:10 +0200	[thread overview]
Message-ID: <CANXojcywrY3eRan+Z6CmdfTrDhyeo9DVa4COnTvVQ2=XD-4GVw@mail.gmail.com> (raw)
In-Reply-To: <CAJfpegveErYS8+23eNejT8K9Gimtw9w2kXRpyqhqQVSwCFBHgg@mail.gmail.com>

2016-05-31 9:17 GMT+02:00 Miklos Szeredi <miklos@szeredi.hu>:
> On Tue, May 31, 2016 at 9:08 AM, Stef Bon <stefbon@gmail.com> wrote:
>> Hi,
>>

>
> The problem would be if the fuse filesystem assumed serialized
> lookup/readdir and they don't do any locking themselves.
>

Yes of course.

> 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).

Yes, via a init flag, where serialization will be the default to
provide backwards compatibility.
You say "re-add". Has this been in the kernel module before?

Stef

  reply	other threads:[~2016-05-31 10:57 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 [this message]
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='CANXojcywrY3eRan+Z6CmdfTrDhyeo9DVa4COnTvVQ2=XD-4GVw@mail.gmail.com' \
    --to=stefbon@gmail.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    /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).