From: Andy Adamson <andros@thnk.citi.umich.edu>
To: linux-fsdevel@vger.kernel.org
Cc: nfsv4@linux-nfs.org, willy@debian.org
Subject: [PATCH 2 of 10] RESEND lease interfaces for version 4 NFSD
Date: Tue, 21 Sep 2004 18:35:45 -0400 [thread overview]
Message-ID: <1095804047.21441d5b.2@citi.umich.edu> (raw)
VFS: add a lock manager release private callback to locks_free_lock() for lock
manger lease clean-up.
Signed-off-by: Andy Adamson <andros@citi.umich.edu>
---
linux-2.6.9-rc2-andros/fs/locks.c | 7 ++++++-
linux-2.6.9-rc2-andros/include/linux/fs.h | 1 +
2 files changed, 7 insertions(+), 1 deletion(-)
diff -puN fs/locks.c~lmops-release-priv fs/locks.c
--- linux-2.6.9-rc2/fs/locks.c~lmops-release-priv 2004-09-21 18:00:23.069460088 -0400
+++ linux-2.6.9-rc2-andros/fs/locks.c 2004-09-21 18:00:23.076459024 -0400
@@ -172,7 +172,12 @@ static inline void locks_free_lock(struc
fl->fl_ops->fl_release_private(fl);
fl->fl_ops = NULL;
}
- fl->fl_lmops = NULL;
+
+ if (fl->fl_lmops) {
+ if (fl->fl_lmops->fl_release_private)
+ fl->fl_lmops->fl_release_private(fl);
+ fl->fl_lmops = NULL;
+ }
kmem_cache_free(filelock_cache, fl);
}
diff -puN include/linux/fs.h~lmops-release-priv include/linux/fs.h
--- linux-2.6.9-rc2/include/linux/fs.h~lmops-release-priv 2004-09-21 18:00:23.071459784 -0400
+++ linux-2.6.9-rc2-andros/include/linux/fs.h 2004-09-21 18:00:23.077458872 -0400
@@ -634,6 +634,7 @@ struct lock_manager_operations {
int (*fl_compare_owner)(struct file_lock *, struct file_lock *);
void (*fl_notify)(struct file_lock *); /* unblock callback */
void (*fl_copy_lock)(struct file_lock *, struct file_lock *);
+ void (*fl_release_private)(struct file_lock *);
};
/* that will die - we need it for nfs_lock_info */
_
reply other threads:[~2004-09-21 22:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1095804047.21441d5b.2@citi.umich.edu \
--to=andros@thnk.citi.umich.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nfsv4@linux-nfs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).