From: Andi Kleen <ak@suse.de>
To: Jonathan Lundell <jlundell@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ENOIOCTLCMD?
Date: Sat, 12 May 2001 11:11:23 +0200 [thread overview]
Message-ID: <20010512111123.A27451@gruyere.muc.suse.de> (raw)
In-Reply-To: <p05100302b7226d91e632@[207.213.214.37]>
In-Reply-To: <p05100302b7226d91e632@[207.213.214.37]>; from jlundell@pobox.com on Fri, May 11, 2001 at 10:01:50PM -0700
On Fri, May 11, 2001 at 10:01:50PM -0700, Jonathan Lundell wrote:
> Can somebody explain the use of ENOIOCTLCMD? There are order of 170
> uses in the kernel, but I don't see any guidelines for that use (nor
> what prevents it from being seen by user programs).
The idea with ENOIOCTLCMD is that when you have multiple subsystem
callbacks (e.g. to low level drivers) the higher levels can pass the ioctls
down and they return ENOIOCTLCMD when they don't know the ioctl number,
so other subsystems can be tried.
This is nicer than using EINVAL, because EINVAL is a terminal condition.
The higher layer should always convert it into EINVAL if there is not
another callback to call, but if it leaks it is probably a bug.
-Andi
next prev parent reply other threads:[~2001-05-12 9:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-12 5:01 ENOIOCTLCMD? Jonathan Lundell
2001-05-12 9:11 ` Andi Kleen [this message]
2001-05-12 11:16 ` ENOIOCTLCMD? Alan Cox
2001-05-12 13:40 ` ENOIOCTLCMD? Mark H. Wood
2001-05-12 14:52 ` ENOIOCTLCMD? Jonathan Lundell
2001-05-12 16:43 ` ENOIOCTLCMD? Alan Cox
2001-05-13 15:15 ` ENOIOCTLCMD? Jonathan Lundell
2001-05-13 16:45 ` ENOIOCTLCMD? Alan Cox
2001-05-13 17:48 ` ENOIOCTLCMD? Jonathan Lundell
2001-05-12 22:27 ` ENOIOCTLCMD? Shane Wegner
2001-05-13 15:17 ` ENOIOCTLCMD? Jonathan Lundell
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=20010512111123.A27451@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=jlundell@pobox.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®