From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Max Krasnyansky <maxk@qualcomm.com>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH RFC 1/5] vringfd syscall
Date: Wed, 09 Apr 2008 14:28:05 -0500 [thread overview]
Message-ID: <47FD18C5.6040709@goop.org> (raw)
In-Reply-To: <200804052202.09157.rusty@rustcorp.com.au>
Rusty Russell wrote:
> +asmlinkage long sys_vringfd(void __user *addr,
> + unsigned num_descs,
> + u16 __user *last_used)
> +{
> + int fd, err;
> + struct file *filp;
> + struct vring_info *vr;
> +
> + /* Must be a power of two, and representable by u16 */
> + if (!num_descs || (num_descs & (num_descs-1)) || num_descs > 65536) {
>
65536 doesn't fit in u16.
J
next prev parent reply other threads:[~2008-04-09 19:28 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 12:02 [PATCH RFC 1/5] vringfd syscall Rusty Russell
2008-04-05 12:04 ` [PATCH RFC 2/5] vringfd base/offset Rusty Russell
2008-04-05 12:05 ` [PATCH RFC 3/5] tun: vringfd receive support Rusty Russell
2008-04-05 17:26 ` Anthony Liguori
2008-04-05 17:26 ` Anthony Liguori
2008-04-05 12:05 ` Rusty Russell
2008-04-05 12:06 ` [PATCH RFC 4/5] tun: vringfd xmit support Rusty Russell
2008-04-05 12:06 ` Rusty Russell
2008-04-05 12:09 ` [PATCH RFC 5/5] lguest support Rusty Russell
2008-04-05 12:09 ` Rusty Russell
2008-04-07 5:13 ` [PATCH RFC 4/5] tun: vringfd xmit support Herbert Xu
2008-04-07 5:13 ` Herbert Xu
2008-04-07 7:24 ` Rusty Russell
2008-04-07 7:35 ` David Miller
2008-04-08 1:51 ` Rusty Russell
2008-04-08 1:51 ` Rusty Russell
2008-04-07 7:35 ` David Miller
2008-04-07 7:24 ` Rusty Russell
2008-04-08 19:49 ` [PATCH RFC 3/5] tun: vringfd receive support Max Krasnyansky
2008-04-09 12:46 ` Dor Laor
2008-04-09 12:46 ` Dor Laor
2008-04-10 17:02 ` Max Krasnyanskiy
2008-04-10 17:02 ` Max Krasnyanskiy
2008-04-10 5:44 ` Rusty Russell
2008-04-10 5:44 ` Rusty Russell
2008-04-10 17:18 ` Max Krasnyanskiy
2008-04-10 17:18 ` Max Krasnyanskiy
2008-04-08 19:49 ` Max Krasnyansky
2008-04-05 12:44 ` [PATCH RFC 2/5] vringfd base/offset Avi Kivity
2008-04-06 2:54 ` Rusty Russell
2008-04-06 2:54 ` Rusty Russell
2008-04-05 12:44 ` Avi Kivity
2008-04-08 5:14 ` Arnd Bergmann
2008-04-08 5:14 ` Arnd Bergmann
2008-04-05 12:04 ` Rusty Russell
2008-04-05 17:18 ` Anthony Liguori
2008-04-06 3:23 ` Rusty Russell
2008-04-06 3:23 ` Rusty Russell
2008-04-05 17:18 ` Anthony Liguori
2008-04-07 17:54 ` [PATCH RFC 1/5] vringfd syscall Jonathan Corbet
2008-04-07 22:34 ` Rusty Russell
2008-04-07 22:34 ` Rusty Russell
2008-04-07 17:54 ` Jonathan Corbet
2008-04-08 2:35 ` Arnd Bergmann
2008-04-08 2:35 ` Arnd Bergmann
2008-04-08 2:35 ` Arnd Bergmann
2008-04-09 19:28 ` Jeremy Fitzhardinge
2008-04-09 19:28 ` Jeremy Fitzhardinge [this message]
2008-04-12 17:18 ` Marcelo Tosatti
2008-04-12 17:18 ` Marcelo Tosatti
2008-04-12 17:39 ` Marcelo Tosatti
2008-04-12 17:39 ` Marcelo Tosatti
2008-04-12 18:19 ` Rusty Russell
2008-04-12 18:19 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2008-04-05 12:02 Rusty Russell
2008-04-05 17:13 ` Anthony Liguori
2008-04-06 3:03 ` Rusty Russell
2008-04-06 3:03 ` Rusty Russell
2008-04-05 17:13 ` Anthony Liguori
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=47FD18C5.6040709@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.