From: Eric Biggers <ebiggers3@gmail.com>
To: fuse-devel@lists.sourceforge.net
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mszeredi@suse.cz
Subject: [BUG] fuse: request prepared before protocol version is known
Date: Tue, 23 Dec 2014 11:58:03 -0600 [thread overview]
Message-ID: <20141223175803.GA9789@zzz> (raw)
I am using Linux 3.19-rc1 and I encountered a bug where stat() would
sporatically fail with EIO when called on a file in a FUSE filesystem very
shortly after that filesystem has been mounted. This is a regression caused by
commit 7078187a: "fuse: introduce fuse_simple_request() helper".
The underlying issue is that the arguments to the FUSE request are being
initialized before the protocol version (fc->minor) is known. This was not a
problem with the old code because fuse_get_req() will wait until the channel has
been initialized.
The only potential solutions I have in mind are adding an explicit waits in all
the needed places, or reverting the commit.
Eric
next reply other threads:[~2014-12-23 17:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 17:58 Eric Biggers [this message]
2015-01-08 14:14 ` [fuse-devel] [BUG] fuse: request prepared before protocol version is known Miklos Szeredi
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=20141223175803.GA9789@zzz \
--to=ebiggers3@gmail.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@suse.cz \
/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).