From: Sander Eikelenboom <linux@eikelenboom.it>
To: Kirill Smelkov <kirr@nexedi.com>,
Miklos Szeredi <mszeredi@redhat.com>,
gluster-devel@gluster.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Linux 5.2-RC regression bisected, mounting glusterfs volumes fails after commit: fuse: require /dev/fuse reads to have enough buffer capacity
Date: Tue, 11 Jun 2019 12:46:38 +0200 [thread overview]
Message-ID: <876aefd0-808a-bb4b-0897-191f0a8d9e12@eikelenboom.it> (raw)
L.S.,
While testing a linux 5.2 kernel I noticed it fails to mount my glusterfs volumes.
It repeatedly fails with:
[2019-06-11 09:15:27.106946] W [fuse-bridge.c:4993:fuse_thread_proc] 0-glusterfs-fuse: read from /dev/fuse returned -1 (Invalid argument)
[2019-06-11 09:15:27.106955] W [fuse-bridge.c:4993:fuse_thread_proc] 0-glusterfs-fuse: read from /dev/fuse returned -1 (Invalid argument)
[2019-06-11 09:15:27.106963] W [fuse-bridge.c:4993:fuse_thread_proc] 0-glusterfs-fuse: read from /dev/fuse returned -1 (Invalid argument)
[2019-06-11 09:15:27.106971] W [fuse-bridge.c:4993:fuse_thread_proc] 0-glusterfs-fuse: read from /dev/fuse returned -1 (Invalid argument)
etc.
etc.
Bisecting turned up as culprit:
commit d4b13963f217dd947da5c0cabd1569e914d21699: fuse: require /dev/fuse reads to have enough buffer capacity
The glusterfs version i'm using is from Debian stable:
ii glusterfs-client 3.8.8-1 amd64 clustered file-system (client package)
ii glusterfs-common 3.8.8-1 amd64 GlusterFS common libraries and translator modules
A 5.1.* kernel works fine, as does a 5.2-rc4 kernel with said commit reverted.
--
Sander
next reply other threads:[~2019-06-11 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 10:46 Sander Eikelenboom [this message]
2019-06-11 11:52 ` Miklos Szeredi
2019-06-11 20:27 ` Kirill Smelkov
2019-06-12 7:44 ` Miklos Szeredi
2019-06-12 11:25 ` [PATCH] fuse: require /dev/fuse reads to have enough buffer capacity (take 2) Kirill Smelkov
2019-06-12 12:11 ` Sander Eikelenboom
2019-06-12 13:03 ` Sander Eikelenboom
2019-06-12 14:12 ` Kirill Smelkov
2019-06-12 16:28 ` Sander Eikelenboom
2019-06-12 17:03 ` Kirill Smelkov
2019-06-23 7:26 ` [PATCH, RESEND] " Kirill Smelkov
2019-07-08 17:03 ` [PATCH, RESEND2] " Kirill Smelkov
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=876aefd0-808a-bb4b-0897-191f0a8d9e12@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=gluster-devel@gluster.org \
--cc=kirr@nexedi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®