All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	stsp <stsp2@yandex.ru>,
	linux-serial@vger.kernel.org,
	Linux kernel <linux-kernel@vger.kernel.org>,
	Johan Hovold <johan@kernel.org>
Subject: Re: [regression] ENOTTY returned for tty fds
Date: Wed, 31 Jul 2024 12:25:43 +0200	[thread overview]
Message-ID: <2024073111-probe-endanger-cc8c@gregkh> (raw)
In-Reply-To: <ZqDeTlq-1NP3dne_@gondor.apana.org.au>

On Wed, Jul 24, 2024 at 06:58:22PM +0800, Herbert Xu wrote:
> On Wed, Jul 24, 2024 at 06:53:00PM +0800, Herbert Xu wrote:
> > On Wed, Jul 24, 2024 at 12:15:39PM +0200, Greg KH wrote:
> > >
> > > -ENOTTY is the documented result of invalid ioctl arguments sent, I am
> > > pretty sure POSIX requires this somewhere.  So this was fixing a
> > > requirement here...
> > 
> > POSIX does not specify this at all:
> > 
> > https://pubs.opengroup.org/onlinepubs/9699919799/functions/ioctl.html
> 
> In fact it says:
> 
> If an underlying device driver detects an error, then ioctl() shall fail if:
> 
> [EINVAL]
> The request or arg argument is not valid for this device.
> 
> [ENOTTY]
> The file associated with the fildes argument is not a STREAMS device that accepts control functions.
> 
> Of course this is all moot since POSIX only specifies ioctl(2)
> for STREAMS devices, but this patch in question is literally
> going against the woring here.

That's going to be going against a lot of existing kernel code then.
-ENOTTY is the default action of almost all ioctl handlers when the
command is not a valid one, sorry.

thanks,

greg k-h

  reply	other threads:[~2024-07-31 10:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-21 11:52 [regression] ENOTTY returned for tty fds stsp
2024-07-24  6:51 ` Greg KH
2024-07-24  8:07   ` stsp
2024-07-24  9:08     ` Greg KH
2024-07-24  9:55       ` stsp
2024-07-24 10:15         ` Greg KH
2024-07-24 10:53           ` Herbert Xu
2024-07-24 10:58             ` Herbert Xu
2024-07-31 10:25               ` Greg KH [this message]
2024-07-31 16:12                 ` Johan Hovold

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=2024073111-probe-endanger-cc8c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=stsp2@yandex.ru \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.