From: Andi Kleen <ak@suse.de>
To: Alexey Toptygin <alexeyt@freeshell.org>
Cc: linux-kernel@vger.kernel.org, tony.luck@intel.com
Subject: Re: [PATCH] sendfile compat functions on x86_64 and ia64
Date: Sat, 6 May 2006 10:46:24 +0200 [thread overview]
Message-ID: <200605061046.24315.ak@suse.de> (raw)
In-Reply-To: <Pine.NEB.4.62.0605052145140.25706@ukato.freeshell.org>
> I agree that this test will pass if we change the declaration of count to
> u32 in sys32_sendfile,
Again the compat layer is only supposed to be as good as a native 32bit
kernel. You try to make it better by allowing values that a 32bit
kernel wouldn't allow. But that's not its goal - it just wants to be
as compatible as possible.
> The only thing my patch does other than changing the signedness of count
> in the declaration of x86_64 sys32_sendfile is relabelling the types of
> offset and count to compat_off_t and compat_size_t. The underlying types
> shouldn't change as a result, but I think this way what is going on is
> much clearer: the compat_ types were defined for exactly this scenario of
> 64 bit kernel functions getting off_t and size_t values from a 32 bit
> userland, no?
The goal isn't to be clear, the goal is to be compatible.
Please stop continue arguing about this - it's useless.
-Andi
next prev parent reply other threads:[~2006-05-06 8:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 0:45 [PATCH] sendfile compat functions on x86_64 and ia64 Alexey Toptygin
2006-05-05 20:38 ` Andi Kleen
2006-05-05 20:44 ` Alexey Toptygin
2006-05-05 21:28 ` Andi Kleen
2006-05-05 22:19 ` Alexey Toptygin
2006-05-06 8:46 ` Andi Kleen [this message]
2006-05-06 22:43 ` Alexey Toptygin
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=200605061046.24315.ak@suse.de \
--to=ak@suse.de \
--cc=alexeyt@freeshell.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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