From: Miklos Szeredi <miklos@szeredi.hu>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: fuse-devel <fuse-devel@lists.sourceforge.net>,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
"mszeredi@suse.cz" <mszeredi@suse.cz>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [fuse-devel] [BUG] fuse: request prepared before protocol version is known
Date: Thu, 8 Jan 2015 15:14:18 +0100 [thread overview]
Message-ID: <CAJfpegtqBEZLdhKjXe3VhZe5mp1LvsQRTOjHw3RcnWeqi+U6NA@mail.gmail.com> (raw)
In-Reply-To: <20141223175803.GA9789@zzz>
On Tue, Dec 23, 2014 at 6:58 PM, Eric Biggers <ebiggers3@gmail.com> wrote:
> 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.
Thanks for the report. See for-linus branch of
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
for the fix.
Thanks,
Miklos
prev parent reply other threads:[~2015-01-08 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 17:58 [BUG] fuse: request prepared before protocol version is known Eric Biggers
2015-01-08 14:14 ` Miklos Szeredi [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=CAJfpegtqBEZLdhKjXe3VhZe5mp1LvsQRTOjHw3RcnWeqi+U6NA@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=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).