From: Frank Schruefer <kernel@man-made.de>
To: linux-kernel@vger.kernel.org
Cc: alan@redhat.com
Subject: [TRIVIAL PATCH] Documentation vfs.txt, d_delete prototype
Date: Sat, 02 Jul 2005 06:01:42 +0200 [thread overview]
Message-ID: <42C611A6.9070309@man-made.de> (raw)
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)
reply other threads:[~2005-07-02 4:02 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=42C611A6.9070309@man-made.de \
--to=kernel@man-made.de \
--cc=alan@redhat.com \
--cc=linux-kernel@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