[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
message-id: <3ee-56d97e80-3b-4a1d2580@40597794>
date: Fri, 04 Mar 2016 13:23:48 +0100
from: "Andrew Karpow" <andy@...k.de>
to: "Nikhilesh Reddy" <reddyn@...eaurora.org>
cc: torvalds@...ux-foundation.org,
"Miklos Szeredi" <miklos@...redi.hu>,
"fuse-devel" <fuse-devel@...ts.sourceforge.net>,
linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
gregkh@...uxfoundation.org, linux-fsdevel@...r.kernel.org,
viro@...iv.linux.org.uk, "Richard Weinberger" <richard@....at>,
"Theodore Tso" <tytso@....edu>, jack@...e.cz,
"Antonio SJ Musumeci" <trapexit@...wn.link>, sven.utcke@....de,
"Nikolaus Rath" <nikolaus@...h.org>,
"Jann Horn" <jannhorn@...glemail.com>,
"Mike Shal" <marfey@...il.com>
subject: Re: [fuse-devel] [PATCH v5] fuse: Add support for passthrough
read/write
Hi!
Thanks for the passthrough patch, exactly what I was searching for.
I'am currently trying to port your code to a prehistoric RedHat 6 Kernel, but I wonder about some implementation details...
> +++ b/fs/fuse/passthrough.c
...
> +void fuse_setup_passthrough(struct fuse_conn *fc, struct fuse_req *req)
..
> + daemon_fd = (int)open_out->passthrough_fd;
...
> +++ b/include/uapi/linux/fuse.h
...
> @@ -480,7 +481,7 @@ struct fuse_create_in {
> struct fuse_open_out {
> uint64_t fh;
> uint32_t open_flags;
> - uint32_t padding;
> + int32_t passthrough_fd;
> };
I don't get where the passthrough_fd struct member is ever set?
with best regards,
Andy
Powered by blists - more mailing lists