On 12/6/11 4:55 PM, Eric Sandeen wrote: > after 250df6ed274d767da844a5d9f05720b804240197 > (fs: protect inode->i_state with inode->i_lock), insert_inode_locked() > no longer returns the inode with I_NEW set. However, error handlers Whoops that should say "with I_NEW set on failure" Will resend for the fs patches I copied that text to :( -Eric > still call unlock_new_inode() on failure, which does a WARN_ON if > I_NEW is not set, so any failure spews a lot of warnings. > > Patches follow to skip the call to unlock_new_inode() if > insert_inode_locked() fails. > > -Eric > -- > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
