qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stuart Anderson <anderson@netsweng.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] semaphore syscalls - refresh
Date: Tue, 17 Apr 2007 16:58:01 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0704171656580.22280@trantor.stuart.netsweng.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703312117080.5290@trantor.stuart.netsweng.com>


Thiemo,
 	Just wondering if you had a chance to take another look at
this.


On Sat, 31 Mar 2007, Stuart Anderson wrote:

> On Sat, 31 Mar 2007, Thiemo Seufer wrote:
>
>>> +    switch( cmd ) {
>>> +	case GETALL:
>>> +	case SETALL:
>>> +	case IPC_STAT:
>>> +	case IPC_SET:
>>> +           lock_user_struct(target_su, target_addr, 1);
>>> +	   target_to_host_semid_ds(ds,target_su->buf);
>>> +	   host_su->buf = ds;
>>> +           unlock_user_struct(target_su, target_addr, 0);
>>> +	   break;
>> 
>> I don't see how this can work with target_su being an uninitialized 
>> pointer.
>
> #define lock_user_struct(host_ptr, guest_addr, copy) \
>    host_ptr = lock_user(guest_addr, sizeof(*host_ptr), copy)
>
> target_su is the left hand side of the assignment. The macro just hides it.
>
>
>                                Stuart
>
> Stuart R. Anderson                               anderson@netsweng.com
> Network & Software Engineering                   http://www.netsweng.com/
> 1024D/37A79149:                                  0791 D3B8 9A4C 2CDC A31F
>                                                 BD03 0A62 E534 37A7 9149

      reply	other threads:[~2007-04-17 21:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30  1:30 [Qemu-devel] [PATCH] semaphore syscalls - refresh Stuart Anderson
2007-03-31 18:58 ` Thiemo Seufer
2007-04-01  1:18   ` Stuart Anderson
2007-04-17 20:58     ` Stuart Anderson [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=Pine.LNX.4.64.0704171656580.22280@trantor.stuart.netsweng.com \
    --to=anderson@netsweng.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).