From: Steve French <smfltc@us.ibm.com>
To: linux-cifs-client@cifs.bkbits.net
Cc: linux-fsdevel@vger.kernel.org
Subject: fcntl method for file_operations
Date: 25 Mar 2004 12:04:54 -0600 [thread overview]
Message-ID: <1080237894.2380.5.camel@stevef95.austin.ibm.com> (raw)
> 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).
next reply other threads:[~2004-03-25 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 18:04 Steve French [this message]
2004-03-25 19:35 ` fcntl method for file_operations 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
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=1080237894.2380.5.camel@stevef95.austin.ibm.com \
--to=smfltc@us.ibm.com \
--cc=linux-cifs-client@cifs.bkbits.net \
--cc=linux-fsdevel@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