From: David Miller <davem@davemloft.net>
To: suzuki@in.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Behaviour of compat_msgsnd/compat_msgrcv calls
Date: Wed, 25 Oct 2006 13:49:32 -0700 (PDT) [thread overview]
Message-ID: <20061025.134932.63125874.davem@davemloft.net> (raw)
In-Reply-To: <453FB3F9.9080704@in.ibm.com>
From: Suzuki K P <suzuki@in.ibm.com>
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.
next prev parent reply other threads:[~2006-10-25 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 18:59 Suzuki K P
2006-10-25 20:49 ` David Miller [this message]
2006-11-08 17:36 ` Suzuki K P
2006-11-08 18:27 ` Suzuki K P
2006-11-11 1:24 ` [RFC] [PATCH] Fix compat space msg size limit for msgsnd/msgrcv ( Was Re: Behaviour of compat_msgsnd/compat_msgrcv calls ) 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=20061025.134932.63125874.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=suzuki@in.ibm.com \
/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
Powered by JetHome