From: Pawel Moll <pawel.moll@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Drew Richardson <Drew.Richardson@arm.com>
Subject: Re: [PATCH v2] perf: Handle compat ioctl
Date: Thu, 14 Aug 2014 11:17:48 +0100 [thread overview]
Message-ID: <1408011468.21373.4.camel@hornet> (raw)
In-Reply-To: <20140707124315.GN6758@twins.programming.kicks-ass.net>
On Mon, 2014-07-07 at 13:43 +0100, Peter Zijlstra wrote:
> On Tue, Jul 01, 2014 at 05:06:00PM +0100, Pawel Moll wrote:
> > On Tue, 2014-06-17 at 13:43 +0100, Pawel Moll wrote:
> > > When running a 32-bit userspace on a 64-bit kernel (eg. i386
> > > application on x86_64 kernel or 32-bit arm userspace on arm64
> > > kernel) some of the perf ioctls must be treated with special
> > > care, as they have a pointer size encoded in the command.
> > >
> > > For example, PERF_EVENT_IOC_ID in 32-bit world will be encoded
> > > as 0x80042407, but 64-bit kernel will expect 0x80082407. In
> > > result the ioctl will fail returning -ENOTTY.
> > >
> > > This patch solves the problem by adding code fixing up the
> > > size as compat_ioctl file operation.
> > >
> > > Reported-by: Drew Richardson <drew.richardson@arm.com>
> > > Signed-off-by: Pawel Moll <pawel.moll@arm.com>
> >
> > This just is a polite and friendly nag...
> >
> > Any, strong or not, opinions on the matter?
>
> Sorry, travel, cracks, falling, etc..
>
> Queued it, we'll see what happens with this one ;-)
Has it managed to hold on to the ground between the cracks then? ;-)
(asking because can't see it in your perf/core branch on git.kernel.org)
Pawel
next prev parent reply other threads:[~2014-08-14 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 15:03 [PATCH] perf: Handle compat ioctl Pawel Moll
2014-06-17 12:13 ` Peter Zijlstra
2014-06-17 12:43 ` [PATCH v2] " Pawel Moll
2014-07-01 16:06 ` Pawel Moll
2014-07-07 12:43 ` Peter Zijlstra
2014-08-14 10:17 ` Pawel Moll [this message]
2014-08-14 10:51 ` Peter Zijlstra
2014-08-14 12:25 ` Pawel Moll
2014-06-17 13:19 ` [PATCH] " Pawel Moll
2014-08-20 8:18 ` [tip:perf/urgent] " tip-bot for Pawel Moll
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=1408011468.21373.4.camel@hornet \
--to=pawel.moll@arm.com \
--cc=Drew.Richardson@arm.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.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