From: John Stultz <john.stultz@linaro.org>
To: Colin Cross <ccross@android.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Android Kernel Team <kernel-team@android.com>
Subject: Re: [PATCH] ion_test: Add compat_ioctl support
Date: Thu, 19 Dec 2013 15:30:25 -0800 [thread overview]
Message-ID: <52B38191.9090007@linaro.org> (raw)
In-Reply-To: <CAMbhsRTLL7UfccyLeXraDx53SHXmBoVnKZE8fPcWzB1wsywo_Q@mail.gmail.com>
On 12/19/2013 02:52 PM, Colin Cross wrote:
> On Thu, Dec 19, 2013 at 2:40 PM, John Stultz <john.stultz@linaro.org> wrote:
>> Prior to subitting this, Colin reworked the compat_ioctl support
>> for the ion_test driver, moving the structure to be the same size
>> on both 32 and 64 bit architectures.
>>
>> Two small things were left out. The compat_ioctl ptr assignment,
>> and the fact that despite having uniform sized types in the
>> structure, the structure pads out to different sizes on different
>> arches.
>>
>> This patch resolves this issue by setting the write flag as
>> a __u64, and adding the compat_ioctl ptr.
>>
>> While this does affect the ABI for 32bit users, its only
>> the ABI for the ion_test driver, not ion itself.
>>
>> Cc: Colin Cross <ccross@android.com>
>> Cc: Greg KH <gregkh@linuxfoundation.org>
>> Cc: Android Kernel Team <kernel-team@android.com>
>> Signed-off-by: John Stultz <john.stultz@linaro.org>
>> ---
>> drivers/staging/android/ion/ion_test.c | 1 +
>> drivers/staging/android/uapi/ion_test.h | 2 +-
>> 2 files changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/staging/android/ion/ion_test.c b/drivers/staging/android/ion/ion_test.c
>> index 3e20349..654acb5 100644
>> --- a/drivers/staging/android/ion/ion_test.c
>> +++ b/drivers/staging/android/ion/ion_test.c
>> @@ -231,6 +231,7 @@ static int ion_test_release(struct inode *inode, struct file *file)
>> static const struct file_operations ion_test_fops = {
>> .owner = THIS_MODULE,
>> .unlocked_ioctl = ion_test_ioctl,
>> + .compat_ioctl = ion_test_ioctl,
> Setting the compat_ioctl to the same thing as unlocked_ioctl shouldn't
> be necessary, compat_sys_ioctl will fall through to do_vfs_ioctl if
> compat_ioctl is not set, which will call unlocked_ioctl.
Hrm. I've not looked into the implementation, but doesn't seem to be the
case on x86_64. Without it I get -1 back when calling the ioctl from a
32bit application. With it the ioctls work.
>
>> .open = ion_test_open,
>> .release = ion_test_release,
>> };
>> diff --git a/drivers/staging/android/uapi/ion_test.h b/drivers/staging/android/uapi/ion_test.h
>> index 614d1e3..f1727f5 100644
>> --- a/drivers/staging/android/uapi/ion_test.h
>> +++ b/drivers/staging/android/uapi/ion_test.h
>> @@ -31,7 +31,7 @@ struct ion_test_rw_data {
>> __u64 ptr;
>> __u64 offset;
>> __u64 size;
>> - int write;
>> + __u64 write;
>> };
> Whoops, missed that one. Can you add "int padding" after "int write"
> instead? That at least lets us use the 32 bits later.
Will do.
thanks
-john
next prev parent reply other threads:[~2013-12-19 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 22:40 [PATCH] ion_test: Add compat_ioctl support John Stultz
2013-12-19 22:52 ` Colin Cross
2013-12-19 23:30 ` John Stultz [this message]
2013-12-19 23:45 ` Colin Cross
2013-12-19 23:56 ` [PATCH] ion_test: Add compat_ioctl support (v2) John Stultz
2013-12-20 0:06 ` Colin Cross
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=52B38191.9090007@linaro.org \
--to=john.stultz@linaro.org \
--cc=ccross@android.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--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.