* [TRIVIAL PATCH] Documentation vfs.txt, d_delete prototype
@ 2005-07-02 4:01 Frank Schruefer
0 siblings, 0 replies; only message in thread
From: Frank Schruefer @ 2005-07-02 4:01 UTC (permalink / raw)
To: linux-kernel; +Cc: alan
Hy,
Prototype mismatch in docu (2.6.13-rc1 and earlier):
Stone:/usr/src # diff -r -u linux-2.6.13-rc1.UNTOUCHED linux-2.6.13-rc1
--------------------------------SNIPON---------------------------------------
diff -r -u linux-2.6.13-rc1.UNTOUCHED/Documentation/filesystems/vfs.txt linux-2.6.13-rc1/Documentation/filesystems/vfs.txt
--- linux-2.6.13-rc1.UNTOUCHED/Documentation/filesystems/vfs.txt 2005-06-30 01:00:53.000000000 +0200
+++ linux-2.6.13-rc1/Documentation/filesystems/vfs.txt 2005-07-02 05:04:22.000000000 +0200
@@ -422,7 +422,7 @@
int (*d_revalidate)(struct dentry *);
int (*d_hash) (struct dentry *, struct qstr *);
int (*d_compare) (struct dentry *, struct qstr *, struct qstr *);
- void (*d_delete)(struct dentry *);
+ int (*d_delete)(struct dentry *);
void (*d_release)(struct dentry *);
void (*d_iput)(struct dentry *, struct inode *);
};
@@ -438,7 +438,11 @@
d_delete: called when the last reference to a dentry is
deleted. This means no-one is using the dentry, however it is
- still valid and in the dcache
+ still valid and in the dcache.
+ If the return value is non zero the dentry will be tried to
+ be unhashed and killed.
+ If the return value is zero the behaviour is as if the custom
+ routine wouldn't have been called.
d_release: called when a dentry is really deallocated
-------------------------------SNIPOFF---------------------------------------
--
Thanks,
Frank Schruefer
SITEFORUM Software Europe GmbH
Germany (Thuringia)
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-07-02 4:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-07-02 4:01 [TRIVIAL PATCH] Documentation vfs.txt, d_delete prototype Frank Schruefer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox