From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Alexander Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: Matthew Wilcox <willy@debian.org>,
Steve French <smfltc@us.ibm.com>,
linux-cifs-client@cifs.bkbits.net, linux-fsdevel@vger.kernel.org
Subject: Re: fcntl method for file_operations
Date: Thu, 25 Mar 2004 15:59:05 -0500 [thread overview]
Message-ID: <1080248344.3463.78.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20040325203102.GX31500@parcelfarce.linux.theplanet.co.uk>
På to , 25/03/2004 klokka 15:31, skreiv
viro@parcelfarce.linux.theplanet.co.uk:
> And for that very reason we don't _want_ to make it easy to add new
> piles of vomit into fcntl(). ioctl() is bad enough; until now fcntl()
> was somewhat limited, but typeless method will immediately open the
> floodgates.
If/when it breaks, it will be their problem...
POSIX/SUS both allow you to play the arbitrary interface game with
ioctl(), but nowhere do they sanction it for fcntl()...
> IOW, my vote is strongly against ->fcntl() - the last thing we need
> is yet another multiplexor available to Joe Random Driver-Monkey.
Fair enough. Then I'll put that to akpm, and we'll resend our original
proposal...
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-03-25 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 18:04 fcntl method for file_operations Steve French
2004-03-25 19:35 ` Matthew Wilcox
2004-03-25 19:55 ` Jamie Lokier
2004-03-25 20:15 ` Trond Myklebust
2004-03-25 20:31 ` viro
2004-03-25 20:59 ` Trond Myklebust [this message]
2004-03-25 20:25 ` Steve French
2004-03-25 20:34 ` viro
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=1080248344.3463.78.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-cifs-client@cifs.bkbits.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=smfltc@us.ibm.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox