From: suzuki <suzuki@linux.vnet.ibm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: akpm@osdl.org, davem@davemloft.net, linux-kernel@vger.kernel.org
Subject: Re: + fix-compat-space-msg-size-limit-for-msgsnd-msgrcv.patch added to -mm tree
Date: Tue, 14 Nov 2006 13:22:26 -0800 [thread overview]
Message-ID: <455A3392.6040501@linux.vnet.ibm.com> (raw)
In-Reply-To: <200611141049.36145.arnd@arndb.de>
Hello Arnd,
Arnd Bergmann wrote:
> On Tuesday 14 November 2006 02:28, suzuki wrote:
>
>>I left it as such, inorder to avoid the future changes that may come in
>>the struct msgbuf -if at all-, which would make us to pass every single
>>field as a parameter to do_msgrcv/do_msgsnd.
>
>
> struct msgbuf is part of the kernel ABI and will never change, so that's
> no problem at all.
Ok.
Does the following change look fine ?
do_msgsnd() - Accepting the mtype and user space ptr to the mtext. i.e.,
long do_msgsnd(int msqid, long mtype, void __user *mtext,
size_t msgsz, int msgflg);
and,
do_msgrcv() - accepting the kernel space data ptr to pmtype and user
space ptr to mtext. The caller has to copy the *pmtype back to the user
space.
i.e.,
long do_msgrcv(int msqid, long *pmtype, void __user *mtext,
size_t msgsz, long msgtyp, int msgflg);
or
Can we use the kernel space "struct msgbuf" instead of the mtype being
passed explicitly.
Thanks,
Suzuki
>
> Arnd <><
next prev parent reply other threads:[~2006-11-14 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611132358.kADNwF0V012270@shell0.pdx.osdl.net>
2006-11-14 0:38 ` + fix-compat-space-msg-size-limit-for-msgsnd-msgrcv.patch added to -mm tree Arnd Bergmann
2006-11-14 1:28 ` suzuki
2006-11-14 9:49 ` Arnd Bergmann
2006-11-14 21:22 ` suzuki [this message]
2006-11-14 23:24 ` Arnd Bergmann
2006-11-14 23:30 ` suzuki
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=455A3392.6040501@linux.vnet.ibm.com \
--to=suzuki@linux.vnet.ibm.com \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.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.