From: Andreas Schwab <schwab@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Thierry Vignaud <tvignaud@mandriva.com>,
bugzilla-daemon@bugzilla.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [Bug 14537] New: missing compat_ioctl on x86_64
Date: Wed, 04 Nov 2009 16:41:34 +0100 [thread overview]
Message-ID: <m3d43ys3f5.fsf@hase.home> (raw)
In-Reply-To: <87vdhq8gpc.fsf@basil.nowhere.org> (Andi Kleen's message of "Wed, 04 Nov 2009 16:14:55 +0100")
Andi Kleen <andi@firstfloor.org> writes:
> Thomas Gleixner <tglx@linutronix.de> writes:
>
>>> - with gnome-terminal:
>>> ioctl32(gnome-terminal:1755): Unknown cmd fd(19) cmd(0000530b){t:'S';sz:0}
>>> arg(48111345) on /dev/pts/0
>>> ioctl32(gnome-terminal:1755): Unknown cmd fd(19) cmd(0000530b){t:'S';sz:0}
>>> arg(4811134a) on /dev/pts/0
>>> ioctl32(gnome-terminal:1755): Unknown cmd fd(19) cmd(0000530b){t:'S';sz:0}
>>> arg(48111351) on /dev/pts/0
>>
>> That looks more like an application problem. 'S' is SNDRV_SEQ_IOCTL
>> which has no ioctl nr 0xb. Also I have no idea why a sound sequencer
>> ioctl should work on /dev/pts/0 :)
>
> ioctl numbers are not always unique (I haven't checked if this is the
> case here). But it might be that it's some other ioctl actually.
'S' is also used for streams ioctls, 0x530b is I_FIND.
Andreas.
--
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
next prev parent reply other threads:[~2009-11-04 15:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14537-6666@http.bugzilla.kernel.org/>
2009-11-04 11:43 ` Thomas Gleixner
2009-11-04 15:14 ` Andi Kleen
2009-11-04 15:41 ` Andreas Schwab [this message]
2009-11-04 16:49 ` Randy Dunlap
2009-11-04 22:12 ` Rafael J. Wysocki
2009-11-07 17:20 ` Pavel Machek
2009-11-07 19:06 ` Rafael J. Wysocki
2009-11-07 19:14 ` Pavel Machek
2009-11-07 20:52 ` Arnd Bergmann
2009-11-07 21:10 ` Rafael J. Wysocki
2009-11-07 21:12 ` Arnd Bergmann
2009-11-07 21:14 ` Thomas Gleixner
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=m3d43ys3f5.fsf@hase.home \
--to=schwab@redhat.com \
--cc=andi@firstfloor.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=tvignaud@mandriva.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
all inboxes | Powered by JetHome®