From: Nikolaus Rath <Nikolaus@rath.org>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: commit 5c672ab3f0ee0f78f: fuse: serialize dirops by default
Date: Thu, 10 Nov 2016 20:53:08 -0800 [thread overview]
Message-ID: <87pom2lirv.fsf@vostro.rath.org> (raw)
In-Reply-To: <CAOssrKegTzmzgmGXbAoAivHYBcpqHuWd0o7UO-nWDv8S2ZPCOw@mail.gmail.com> (Miklos Szeredi's message of "Thu, 10 Nov 2016 23:26:31 +0100")
On Nov 10 2016, Miklos Szeredi <mszeredi@redhat.com> wrote:
> On Thu, Nov 10, 2016 at 11:21 PM, Nikolaus Rath <Nikolaus@rath.org> wrote:
>> Hi Miklos,
>>
>> In commit 5c672ab3f0ee0f78f7acad183f34db0f8781a200 you introduced a new
>> FUSE_PARALLEL_DIROPS capability and bumped the kernel interface no to
>> 25 - but there have been no corresponding changes to userspace.
>
> I think libfuse3 should always set this, it's just for backward compatibility.
>
>> Is this still preliminary and thus deliberately not in libfuse? I only
>> noticed it by chance.
>
> Oops, I just forgot about it.
Are you going to send a patch/pull request? If not, I don't mind adding
it either.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
prev parent reply other threads:[~2016-11-11 4:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 22:21 commit 5c672ab3f0ee0f78f: fuse: serialize dirops by default Nikolaus Rath
2016-11-10 22:26 ` Miklos Szeredi
2016-11-11 4:53 ` Nikolaus Rath [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=87pom2lirv.fsf@vostro.rath.org \
--to=nikolaus@rath.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.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 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.