From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [GIT PULL] f2fs updates for v4.2 Date: Thu, 25 Jun 2015 07:29:46 +0100 Message-ID: <20150625062946.GU17109@ZenIV.linux.org.uk> References: <20150624202401.GA40031@jaegeuk-mac02.mot.com> <20150625043334.GT17109@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jaegeuk Kim , Linux Kernel Mailing List , Linux FS Dev Mailing List , Linux F2FS Dev Mailing List , Stephen Rothwell To: Linus Torvalds Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:58580 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751023AbbFYG3v (ORCPT ); Thu, 25 Jun 2015 02:29:51 -0400 Content-Disposition: inline In-Reply-To: <20150625043334.GT17109@ZenIV.linux.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, Jun 25, 2015 at 05:33:34AM +0100, Al Viro wrote: > Said that, f2fs_symlink() looks odd - we create a directory entry *before* > doing page_symlink(). And if it (or encryption) fails, I don't see anything > that would remove that new directory entry. What are we ending up with > in such case? PS: other page_symlink() users tend to do it first and if it fails we just decrement link count and iput() the sucker. BTW, while grepping for that stuff... Why do we have ->delete_inode() set to generic_delete_inode() on ramfs? After all, we never hash the inodes in there, so default will do nicely, and it's kinder of branch prediction - we have if (op->drop_inode) drop = op->drop_inode(inode); else drop = generic_drop_inode(inode); and generic_drop_inode() is inlined there...