From: Nikolaus Rath <Nikolaus@rath.org>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: dhowells@redhat.com, ebiggers@google.com,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
"p.kramme\@profihost.ag" <p.kramme@profihost.ag>,
Daniel Aberger - Profihost AG <d.aberger@profihost.ag>
Subject: Re: Kernel 5.4 breaks fuse 2.X nonempty mount option
Date: Mon, 22 Jun 2020 06:18:17 +0100 [thread overview]
Message-ID: <87pn9rsmp2.fsf@vostro.rath.org> (raw)
In-Reply-To: <736d172c-84ff-3e9f-c125-03ae748218e8@profihost.ag> (Stefan Priebe's message of "Thu, 18 Jun 2020 22:38:25 +0200")
On Jun 18 2020, Stefan Priebe - Profihost AG <s.priebe@profihost.ag> wrote:
> Hi,
>
> while using fuse 2.x and nonempty mount option - fuse mounts breaks
> after upgrading from kernel 4.19 to 5.4.
IIRC nonempty is not processed by the kernel, but libfuse. This sounds like
you did a partial upgrade to libfuse 3.x (which dropped the option).
Best,
Nikolaus
--
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next prev parent reply other threads:[~2020-06-22 5:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 20:38 Kernel 5.4 breaks fuse 2.X nonempty mount option Stefan Priebe - Profihost AG
2020-06-19 5:40 ` Stefan Priebe - Profihost AG
2020-06-19 7:47 ` David Howells
2020-06-19 10:01 ` Daniel Aberger - Profihost AG
2020-06-19 19:02 ` Stefan Priebe - Profihost AG
2020-06-19 19:22 ` Stefan Priebe - Profihost AG
2020-06-21 19:33 ` Stefan Priebe - Profihost AG
2020-06-21 19:49 ` Stefan Priebe - Profihost AG
2020-06-25 19:54 ` Miklos Szeredi
2020-06-25 20:10 ` Stefan Priebe - Profihost AG
2020-06-26 8:34 ` Miklos Szeredi
2020-06-29 12:24 ` Stefan Priebe - Profihost AG
2020-06-29 13:53 ` Miklos Szeredi
2020-06-30 7:04 ` Miklos Szeredi
2020-06-22 5:18 ` Nikolaus Rath [this message]
2020-06-22 6:04 ` Stefan Priebe - Profihost AG
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=87pn9rsmp2.fsf@vostro.rath.org \
--to=nikolaus@rath.org \
--cc=d.aberger@profihost.ag \
--cc=dhowells@redhat.com \
--cc=ebiggers@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=p.kramme@profihost.ag \
--cc=s.priebe@profihost.ag \
--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 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.