Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933228AbdC3Kve (ORCPT ); Thu, 30 Mar 2017 06:51:34 -0400 Received: from b.ns.miles-group.at ([95.130.255.144]:44724 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S932582AbdC3Kvc (ORCPT ); Thu, 30 Mar 2017 06:51:32 -0400 Subject: Re: [PATCH] ubifs: Fix O_TMPFILE corner case in ubifs_link() To: Amir Goldstein References: <1490864181-2192-1-git-send-email-richard@nod.at> <4c7a176b-6132-7936-a04f-d4def5e56320@nod.at> Cc: Adrian Hunter , linux-mtd@lists.infradead.org, linux-kernel , Artem Bityutskiy , "stable [v4.9]" , Ralph Sennhauser From: Richard Weinberger Message-ID: <54320a7a-5022-732f-5a5d-5ec4ca5a4d9e@nod.at> Date: Thu, 30 Mar 2017 12:51:27 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 725 Lines: 22 Amir, Am 30.03.2017 um 12:35 schrieb Amir Goldstein: >> Reading deeper into the proved that I was wrong. >> AFAIKT UBIFS' journal has currently no way to revive a deleted inode. >> So, we have to think about a new solution. >> > > Not that I know anything about ubifs, but why do you need the deleted > inode record in the first place for an O_TMPFILE. > vfs ensures you that you can only link back an O_TMPFILE, not a deleted > inode. > > It does not appear to be the right thing to do to pass deletion=1 to > ubifs_jnl_update(), but deletion=0 doesn't look right as well.. We need to think of a new case. I choose deletion=1 to ensure that after a power-cut written data of the tmpfile gets removed. Thanks, //richard