From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-dev@ozlabs•org, Geert Uytterhoeven <geert@linux-m68k•org>
Cc: Johannes Berg <johannes@sipsolutions•net>
Subject: Re: ioctl32 unknown cmds with 2.6.24-rc1
Date: Wed, 24 Oct 2007 16:27:17 +0200 [thread overview]
Message-ID: <200710241627.18284.arnd@arndb.de> (raw)
In-Reply-To: <1193229045.4510.35.camel@johannes.berg>
On Wednesday 24 October 2007, Johannes Berg wrote:
> Show Details
> I've been getting these warnings (many more of them but this is a list
> of unique ones) on my quad G5 with 32-bit userspace:
>
> ioctl32(cdrom_id:1078): Unknown cmd fd(3) cmd(00005331){t:'S';sz:0} arg(00000000) on /dev/.tmp-3-0
> ioctl32(ata_id:1095): Unknown cmd fd(3) cmd(0000030d){t:03;sz:0} arg(ff863970) on /dev/.tmp-3-0
> ioctl32(smartd:3563): Unknown cmd fd(3) cmd(0000031f){t:03;sz:0} arg(ffeb5480) on /dev/sda
> ioctl32(hald-probe-stor:3761): Unknown cmd fd(4) cmd(00005320){t:'S';sz:0} arg(00000004) on /dev/hda
> ioctl32(gnome-terminal:4187): Unknown cmd fd(19) cmd(0000530b){t:'S';sz:0} arg(0fd8e400) on /dev/pts/0
>
> Does anybody know whether this is expected?
It's probably my fault, since I changed the compat ioctl handling for
block devices. Geert already reported the same, but I haven't had
a chance to reproduce it on my system to look into what went wrong.
Probably a trivial bug I introduced in block/compat_ioctl.c
Arnd <><
next prev parent reply other threads:[~2007-10-24 14:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 12:30 ioctl32 unknown cmds with 2.6.24-rc1 Johannes Berg
2007-10-24 14:27 ` Arnd Bergmann [this message]
2007-10-25 13:38 ` Johannes Berg
2007-10-25 13:45 ` Geert Uytterhoeven
2007-10-25 14:20 ` Arnd Bergmann
2007-10-25 14:51 ` Geert Uytterhoeven
2007-10-25 15:19 ` Arnd Bergmann
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=200710241627.18284.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=geert@linux-m68k$(echo .)org \
--cc=johannes@sipsolutions$(echo .)net \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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