diff options
| author | Christoph Hellwig <hch@lst.de> | 2009-08-07 14:38:25 -0300 |
|---|---|---|
| committer | Christoph Hellwig <hch@brick.lst.de> | 2009-08-07 14:38:25 -0300 |
| commit | 54e346215e4fe2ca8c94c54e546cc61902060510 (patch) | |
| tree | 9b4ed9b0ab78117ba1a41db7073708031622cf10 /include/linux | |
| parent | 90bc1a658a53f8832ee799685703977a450e5af9 (diff) | |
| download | kernel-crypto-54e346215e4fe2ca8c94c54e546cc61902060510.tar.gz kernel-crypto-54e346215e4fe2ca8c94c54e546cc61902060510.tar.xz kernel-crypto-54e346215e4fe2ca8c94c54e546cc61902060510.zip | |
vfs: fix inode_init_always calling convention
Currently inode_init_always calls into ->destroy_inode if the additional
initialization fails. That's not only counter-intuitive because
inode_init_always did not allocate the inode structure, but in case of
XFS it's actively harmful as ->destroy_inode might delete the inode from
a radix-tree that has never been added. This in turn might end up
deleting the inode for the same inum that has been instanciated by
another process and cause lots of cause subtile problems.
Also in the case of re-initializing a reclaimable inode in XFS it would
free an inode we still want to keep alive.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Eric Sandeen <sandeen@sandeen.net>
Diffstat (limited to 'include/linux')
| -rw-r--r-- | include/linux/fs.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/include/linux/fs.h b/include/linux/fs.h index a36ffa5a77a..0c3b5e58a98 100644 --- a/include/linux/fs.h +++ b/include/linux/fs.h @@ -2137,7 +2137,7 @@ extern loff_t default_llseek(struct file *file, loff_t offset, int origin); extern loff_t vfs_llseek(struct file *file, loff_t offset, int origin); -extern struct inode * inode_init_always(struct super_block *, struct inode *); +extern int inode_init_always(struct super_block *, struct inode *); extern void inode_init_once(struct inode *); extern void inode_add_to_lists(struct super_block *, struct inode *); extern void iput(struct inode *); |