From: "Andrew Karpow" <andy@ndyk.de>
To: "Nikhilesh Reddy" <reddyn@codeaurora.org>
Cc: torvalds@linux-foundation.org,
"Miklos Szeredi" <miklos@szeredi.hu>,
"fuse-devel" <fuse-devel@lists.sourceforge.net>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
gregkh@linuxfoundation.org, linux-fsdevel@vger.kernel.org,
viro@zeniv.linux.org.uk, "Richard Weinberger" <richard@nod.at>,
"Theodore Tso" <tytso@mit.edu>,
jack@suse.cz, "Antonio SJ Musumeci" <trapexit@spawn.link>,
sven.utcke@gmx.de, "Nikolaus Rath" <nikolaus@rath.org>,
"Jann Horn" <jannhorn@googlemail.com>,
"Mike Shal" <marfey@gmail.com>
Subject: Re: [fuse-devel] [PATCH v5] fuse: Add support for passthrough read/write
Date: Fri, 04 Mar 2016 13:23:48 +0100 [thread overview]
Message-ID: <3ee-56d97e80-3b-4a1d2580@40597794> (raw)
In-Reply-To: <56AFAA5B.3000006@codeaurora.org>
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
prev parent reply other threads:[~2016-03-04 12:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 18:56 [PATCH v5] fuse: Add support for passthrough read/write Nikhilesh Reddy
2016-02-01 19:15 ` Jann Horn
2016-02-01 19:28 ` Nikhilesh Reddy
2016-02-01 19:45 ` Jann Horn
2016-02-03 19:05 ` Nikhilesh Reddy
2016-02-03 19:56 ` Jann Horn
2016-02-02 8:10 ` Jann Horn
2016-02-03 19:05 ` Nikhilesh Reddy
2016-02-03 19:53 ` Jann Horn
2016-02-03 20:16 ` Nikhilesh Reddy
2016-02-03 20:42 ` Jann Horn
2016-03-04 12:23 ` Andrew Karpow [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=3ee-56d97e80-3b-4a1d2580@40597794 \
--to=andy@ndyk.de \
--cc=fuse-devel@lists.sourceforge.net \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=jannhorn@googlemail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marfey@gmail.com \
--cc=miklos@szeredi.hu \
--cc=nikolaus@rath.org \
--cc=reddyn@codeaurora.org \
--cc=richard@nod.at \
--cc=sven.utcke@gmx.de \
--cc=torvalds@linux-foundation.org \
--cc=trapexit@spawn.link \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).