Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1409922 > unrolled thread

Re: [fuse-devel] Changes in 4.7.

Started byMiklos Szeredi <miklos@szeredi.hu>
First post2016-05-31 09:20 +0200
Last post2016-05-31 09:20 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [fuse-devel] Changes in 4.7. Miklos Szeredi <miklos@szeredi.hu> - 2016-05-31 09:20 +0200

#1409922 — Re: [fuse-devel] Changes in 4.7.

FromMiklos Szeredi <miklos@szeredi.hu>
Date2016-05-31 09:20 +0200
SubjectRe: [fuse-devel] Changes in 4.7.
Message-ID<rEM82-7Tq-13@gated-at.bofh.it>
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

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web