On Fri, Sep 04, 2020 at 12:05:20PM -0400, Jeff Layton wrote: > Ceph needs to be able to allocate inodes ahead of a create that might > involve a fscrypt-encrypted inode. new_inode() almost fits the bill, > but it puts the inode on the sb->s_inodes list, and we don't want to > do that until we're ready to insert it into the hash. > > Signed-off-by: Jeff Layton <jlayton@xxxxxxxxxx> > --- > fs/inode.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/fs/inode.c b/fs/inode.c > index 72c4c347afb7..61554c2477ab 100644 > --- a/fs/inode.c > +++ b/fs/inode.c > @@ -935,6 +935,7 @@ struct inode *new_inode_pseudo(struct super_block *sb) > } > return inode; > } > +EXPORT_SYMBOL(new_inode_pseudo); > What's the problem with putting the new inode on sb->s_inodes already? That's what all the other filesystems do. - Eric
|