From: Peter Braam <braam@clusterfs.com>
To: David Woodhouse <dwmw2@infradead.org>,
Matthew Wilcox <willy@debian.org>,
intermezzo-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] remove TCGETS
Date: Wed, 13 Aug 2003 19:28:18 -0600 [thread overview]
Message-ID: <20030814012818.GD1918@localhost.localdomain> (raw)
In-Reply-To: <20030813093521.F3708@schatzie.adilger.int>
In fact some part of POSIX says that ioctls should return EINVAL
that's why I made that choice. Anyway, the issue is moot.
- Peter -
On Wed, Aug 13, 2003 at 09:35:21AM -0600, Andreas Dilger wrote:
> On Aug 13, 2003 13:12 +0100, David Woodhouse wrote:
> > On Tue, 2003-08-12 at 22:59, Andreas Dilger wrote:
> > > On Aug 12, 2003 22:48 +0100, Matthew Wilcox wrote:
> > > > I see no reason to handle TCGETS in presto_ioctl, and even if you do get
> > > > it somehow, the action is the same as the default. This happens to break
> > > > on PA-RISC and not on i386 due to i386 using an old-style definition of
> > > > TCGETS and PA-RISC using one which invovles sizeof().
> > > >
> > > > diff -urpNX dontdiff linus-2.6/fs/intermezzo/dir.c parisc-2.6/fs/intermezzo/dir.c
> > > > --- linus-2.6/fs/intermezzo/dir.c Tue Aug 12 13:11:17 2003
> > > > +++ parisc-2.6/fs/intermezzo/dir.c Tue Aug 12 13:29:43 2003
> > > > @@ -1304,10 +1304,6 @@ int presto_ioctl(struct inode *inode, st
> > > > return rc;
> > > > }
> > > >
> > > > - case TCGETS:
> > > > - EXIT;
> > > > - return -EINVAL;
> > > > -
> > > > default:
> > > > EXIT;
> > > > return -EINVAL;
> > >
> > > I can tell you why this was originally in there - because the "default" case
> > > used to print out an error message for unhandled ioctls. Perl used to call
> > > TCGETS all the time on files in lustre, so we put in the no-op case to shut
> > > up the error messages. Now that the error messages are gone from the default
> > > case there is no need to have this there anymore, so removing it is fine.
> >
> > Why was it returning -EINVAL instead of -ENOTTY?
>
> An oversight. Returning -ENOTTY is what I would do today.
>
> Cheers, Andreas
> --
> Andreas Dilger
> http://sourceforge.net/projects/ext2resize/
> http://www-mddsp.enel.ucalgary.ca/People/adilger/
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> intermezzo-devel mailing list
> intermezzo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/intermezzo-devel
- Peter -
next prev parent reply other threads:[~2003-08-14 1:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 21:48 [PATCH] remove TCGETS Matthew Wilcox
2003-08-12 21:59 ` Andreas Dilger
2003-08-13 1:42 ` Peter Braam
2003-08-13 12:12 ` David Woodhouse
2003-08-13 15:35 ` Andreas Dilger
2003-08-14 1:28 ` Peter Braam [this message]
2003-08-14 1:43 ` Matthew Wilcox
2003-08-14 15:54 ` Bryan Henderson
2003-10-28 15:56 ` David Woodhouse
2003-10-28 19:41 ` Bryan Henderson
2003-10-28 20:52 ` Andries Brouwer
2003-10-28 21:07 ` Linus Torvalds
2003-10-28 23:51 ` Andrew Sharp
2003-10-29 1:54 ` Linus Torvalds
2003-10-29 0:46 ` David Woodhouse
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=20030814012818.GD1918@localhost.localdomain \
--to=braam@clusterfs.com \
--cc=dwmw2@infradead.org \
--cc=intermezzo-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=willy@debian.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.