From: Marek Szyprowski <m.szyprowski@samsung.com>
To: "Christian König" <deathsimple@vodafone.de>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH] dma-buf: add support for compat ioctl
Date: Tue, 21 Feb 2017 15:55:02 +0100 [thread overview]
Message-ID: <ac1ddfe4-1667-bdb0-c4da-35c8cf85fbed@samsung.com> (raw)
In-Reply-To: <dbcfe0d9-cdc3-e715-2535-0a2b7ffec3a5@samsung.com>
Dear All,
On 2017-02-21 15:37, Marek Szyprowski wrote:
> Hi Christian,
>
> On 2017-02-21 14:59, Christian König wrote:
>> Am 21.02.2017 um 14:21 schrieb Marek Szyprowski:
>>> Add compat ioctl support to dma-buf. This lets one to use
>>> DMA_BUF_IOCTL_SYNC
>>> ioctl from 32bit application on 64bit kernel. Data structures for
>>> both 32
>>> and 64bit modes are same, so there is no need for additional
>>> translation
>>> layer.
>>
>> Well I might be wrong, but IIRC compat_ioctl was just optional and if
>> not specified unlocked_ioctl was called instead.
>>
>> If that is true your patch wouldn't have any effect at all.
>
> Well, then why I got -ENOTTY in the 32bit test app for this ioctl on
> 64bit ARM64 kernel without this patch?
>
I've checked in fs/compat_ioctl.c, I see no fallback in
COMPAT_SYSCALL_DEFINE3,
so one has to provide compat_ioctl callback to have ioctl working with 32bit
apps.
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next prev parent reply other threads:[~2017-02-21 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170221132114eucas1p2e527d5b5516494ba54aa91f48b3e227f@eucas1p2.samsung.com>
2017-02-21 13:21 ` [PATCH] dma-buf: add support for compat ioctl Marek Szyprowski
2017-02-21 13:59 ` Christian König
2017-02-21 14:37 ` Marek Szyprowski
2017-02-21 14:55 ` Marek Szyprowski [this message]
2017-02-21 15:08 ` Christian König
2017-02-22 19:07 ` Daniel Vetter
2017-02-23 6:37 ` Sumit Semwal
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=ac1ddfe4-1667-bdb0-c4da-35c8cf85fbed@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=deathsimple@vodafone.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox