public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: torvalds@osdl.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/11] FUSE - device functions
Date: Wed, 12 Jan 2005 14:44:02 -0800	[thread overview]
Message-ID: <20050112144402.38a8a337.akpm@osdl.org> (raw)
In-Reply-To: <E1CoOq3-0003Jq-00@dorka.pomaz.szeredi.hu>

Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> +void fuse_send_init(struct fuse_conn *fc)
> +{
> +	/* This is called from fuse_read_super() so there's guaranteed
> +	   to be a request available */
> +	struct fuse_req *req = do_get_request(fc);
> +	struct fuse_init_in_out *arg = &req->misc.init_in_out;
> +	arg->major = FUSE_KERNEL_VERSION;
> +	arg->minor = FUSE_KERNEL_MINOR_VERSION;
> +	req->in.h.opcode = FUSE_INIT;
> +	req->in.numargs = 1;
> +	req->in.args[0].size = sizeof(*arg);
> +	req->in.args[0].value = arg;
> +	req->out.numargs = 1;
> +	req->out.args[0].size = sizeof(*arg);
> +	req->out.args[0].value = arg;

Does all this userspace communication code work OK if it is talking with a
32-bit application from a 64-bit kernel?

Standard question: was netlink considered?

  reply	other threads:[~2005-01-12 22:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 16:25 [PATCH 3/11] FUSE - device functions Miklos Szeredi
2005-01-12 22:44 ` Andrew Morton [this message]
2005-01-13  5:41   ` Miklos Szeredi
  -- strict thread matches above, loose matches on Subject: below --
2005-01-10 19:00 Miklos Szeredi
2005-01-11 17:30 ` Mike Waychison
2005-01-11 19:05   ` 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=20050112144402.38a8a337.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@osdl.org \
    /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