public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Steve French <smfltc@us.ibm.com>
Cc: linux-cifs-client@cifs.bkbits.net, linux-fsdevel@vger.kernel.org
Subject: Re: fcntl method for file_operations
Date: Thu, 25 Mar 2004 19:35:45 +0000	[thread overview]
Message-ID: <20040325193545.GC25059@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1080237894.2380.5.camel@stevef95.austin.ibm.com>

On Thu, Mar 25, 2004 at 12:04:54PM -0600, Steve French wrote:
> > the NFS developers have submitted a patch which adds an fcntl() method
> > to the file_operations structure.
> 
> This patch should be helpful to the cifs vfs for a different reason
> (than the original NFS conflict between O_DIRECT/O_APPEND) , it will
> allow a way to get directory change notification F_NOTIFY (and file open
> notification, F_SETLEASE, perhaps) sent across the network (currenty
> many fcntl calls are meaningful for local filesystems only).

I don't think we should have an fcntl() method.  I'd rather see a typed
set of method calls for whatever set of routines are actually useful.
Something along the lines of ethtool_ops, say ;-)

perhaps the right thing to do is just to add the following ops to
file_operations:

	int (*fcntl_setfl)(int fd, struct file *filp, unsigned long arg);
	int (*fcntl_getlease)(struct file *filp);
	int (*fcntl_setlease)(int fd, struct file *filp, unsigned long arg);
	int (*fcntl_dirnotify(int fd, struct file *filp, unsigned long arg);

comments?

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

  reply	other threads:[~2004-03-25 19:35 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 [this message]
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
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=20040325193545.GC25059@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=linux-cifs-client@cifs.bkbits.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=smfltc@us.ibm.com \
    /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