From: Mikael Pettersson <mikpe@csd.uu.se>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, discuss@x86-64.org, jt@hpl.hp.com
Subject: Re: two x86_64 fixes for 2.4.21-pre3
Date: Mon, 3 Feb 2003 20:17:39 +0100 [thread overview]
Message-ID: <15934.49235.619101.789799@harpo.it.uu.se> (raw)
In-Reply-To: <20030129162824.GA4773@wotan.suse.de>
Andi Kleen writes:
> > 1. One unknown ioctl is logged from RH8.0 init:
> >
> > ioctl32(iwconfig:185): Unknown cmd fd(3) cmd(00008b01){00} arg(ffffda90) on socket:[389]
>
> Probably harmless, but if you figure it out please send me a patch.
The ioctl is SIOCGIWNAME, which is used by iwconfig from the wireless-tools
package to check if a given net dev is a wireless thing or not (called from
ifup in RedHat as a type test on the net dev).
Unfortunately, include/linux/wireless.h has a big pile of ioctls and arg/res
types that would need to be checked, so I'll defer this to Jean Tourrilhes (cc:d).
/Mikael
next prev parent reply other threads:[~2003-02-03 19:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 19:16 Mikael Pettersson
2003-01-24 19:37 ` Andi Kleen
2003-01-28 20:51 ` Mikael Pettersson
2003-01-28 21:27 ` Andi Kleen
2003-01-29 15:39 ` Mikael Pettersson
2003-01-29 16:28 ` Andi Kleen
2003-02-03 19:17 ` Mikael Pettersson [this message]
2003-02-03 19:49 ` Jean Tourrilhes
2003-02-03 20:12 ` Andi Kleen
2003-02-03 21:43 ` Jean Tourrilhes
2003-02-03 22:46 ` 32bit emulation of wireless ioctls Andi Kleen
2003-02-03 23:17 ` Jean Tourrilhes
2003-02-03 23:51 ` Andi Kleen
2003-02-04 0:09 ` Jean Tourrilhes
2003-02-03 23:58 ` David Woodhouse
2003-02-04 0:04 ` David Mosberger
2003-02-04 0:11 ` Anton Blanchard
2003-02-07 10:58 ` two x86_64 fixes for 2.4.21-pre3 Pavel Machek
2003-02-07 14:32 ` Alan Cox
2003-02-07 22:58 ` Erik Mouw
2003-02-04 3:13 ` Ton Hospel
2003-02-04 13:11 ` Mikael Pettersson
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=15934.49235.619101.789799@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=jt@hpl.hp.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 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®