linux-kernel - Re: [fuse-devel] [BUG] fuse: request prepared before protocol version is known

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJfpegtqBEZLdhKjXe3VhZe5mp1LvsQRTOjHw3RcnWeqi+U6NA@mail.gmail.com>
Date:	Thu, 8 Jan 2015 15:14:18 +0100
From:	Miklos Szeredi <miklos@...redi.hu>
To:	Eric Biggers <ebiggers3@...il.com>
Cc:	fuse-devel <fuse-devel@...ts.sourceforge.net>,
	Linux-Fsdevel <linux-fsdevel@...r.kernel.org>,
	"mszeredi@...e.cz" <mszeredi@...e.cz>,
	Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [fuse-devel] [BUG] fuse: request prepared before protocol version
 is known

On Tue, Dec 23, 2014 at 6:58 PM, Eric Biggers <ebiggers3@...il.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/