Re: Behaviour of compat_msgsnd/compat_msgrcv calls

From: Suzuki K P <[email protected]>
Date: Wed, 25 Oct 2006 11:59:05 -0700

> Is there any specific reason behind this ? Can't we just use the user 
> buffer directly instead of doing an additional copy_in_user ?
> ie,
> 	err = sys_msgrcv(first, uptr, second, msgtyp, third);

It's the cleanest way to deal with the difference in
"struct msgbuf" layout between native and compat userspace.

I guess we could make some common do_sys_msgrcv() function
that passed in a pointer to the "msgbuf" and the buffer
seperately.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Behaviour of compat_msgsnd/compat_msgrcv calls
    • From: Suzuki K P <[email protected]>

• References:
  • Behaviour of compat_msgsnd/compat_msgrcv calls
    • From: Suzuki K P <[email protected]>

• Prev by Date: Re: Incorrect order of last two arguments of ptrace for requests PPC_PTRACE_GETREGS, SETREGS, GETFPREGS, SETFPREGS
• Next by Date: Re: Linux and GPL 3
• Previous by thread: Behaviour of compat_msgsnd/compat_msgrcv calls
• Next by thread: Re: Behaviour of compat_msgsnd/compat_msgrcv calls
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]