From: Kirill Korotaev <dev@sw.ru>
To: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: [PATCH] Export of generic_forget_inode()
Date: Sat, 11 Dec 2004 16:36:01 +0300 [thread overview]
Message-ID: <41BAF7C1.4080800@sw.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 321 bytes --]
This patch adds export of generic_forget_inode()
if sb->drop_inode method is set, than it's called in iput_final().
But it's impossible to call neither generic_drop_inode(), nor
generic_forget_inode() inside this handler. Only generic_delete_inode()
is accessiable.
Signed-Off-By: Kirill Korotaev <dev@sw.ru>
Kirill
[-- Attachment #2: diff-export --]
[-- Type: text/plain, Size: 1137 bytes --]
--- ./fs/inode.c.iexp 2004-12-10 17:42:16.000000000 +0300
+++ ./fs/inode.c 2004-12-11 16:33:35.468308456 +0300
@@ -1032,7 +1032,7 @@ void generic_delete_inode(struct inode *
EXPORT_SYMBOL(generic_delete_inode);
-static void generic_forget_inode(struct inode *inode)
+void generic_forget_inode(struct inode *inode)
{
struct super_block *sb = inode->i_sb;
@@ -1059,6 +1059,8 @@ static void generic_forget_inode(struct
destroy_inode(inode);
}
+EXPORT_SYMBOL(generic_forget_inode);
+
/*
* Normal UNIX filesystem behaviour: delete the
* inode when the usage count drops to zero, and
--- ./include/linux/fs.h.iexp 2004-12-10 17:42:17.000000000 +0300
+++ ./include/linux/fs.h 2004-12-11 16:33:31.541905360 +0300
@@ -1393,6 +1393,7 @@ extern struct inode * igrab(struct inode
extern ino_t iunique(struct super_block *, ino_t);
extern int inode_needs_sync(struct inode *inode);
extern void generic_delete_inode(struct inode *inode);
+extern void generic_forget_inode(struct inode *inode);
extern struct inode *ilookup5(struct super_block *sb, unsigned long hashval,
int (*test)(struct inode *, void *), void *data);
next reply other threads:[~2004-12-11 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 13:36 Kirill Korotaev [this message]
2004-12-11 15:24 ` Christoph Hellwig
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=41BAF7C1.4080800@sw.ru \
--to=dev@sw.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®