From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751975AbdBAJ04 (ORCPT ); Wed, 1 Feb 2017 04:26:56 -0500 Received: from lelnx194.ext.ti.com ([198.47.27.80]:47667 "EHLO lelnx194.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751535AbdBAJ0z (ORCPT ); Wed, 1 Feb 2017 04:26:55 -0500 Subject: Re: [PATCH v2] initramfs: finish fput() before accessing any binary from initramfs To: Al Viro , , References: <20170124053636.30121-1-lokeshvutla@ti.com> CC: Linux ARM Mailing List , Tero Kristo , Sekhar Nori , Nishanth Menon , Muralidharan Karicheri From: Lokesh Vutla Message-ID: Date: Wed, 1 Feb 2017 14:54:46 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <20170124053636.30121-1-lokeshvutla@ti.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi All, On Tuesday 24 January 2017 11:06 AM, Lokesh Vutla wrote: > commit 4a9d4b024a31 ("switch fput to task_work_add") implements a > schedule_work() for completing fput(), but did not guarantee calling > __fput() after unpacking initramfs. Because of this, there is a > possibility that during boot a driver can see ETXTBSY when it tries > to load a binary from initramfs as fput() is still pending on that > binary. This patch makes sure that fput() is completed after unpacking > initramfs. > > Reported-by: Murali Karicheri > Signed-off-by: Lokesh Vutla > --- > Link to RFC: https://patchwork.kernel.org/patch/9520539/ > Changes since v1: > - Moved flush_delayed_fput() before loading default modules. > > Note: Reproduced on TI K2HK EVM. K2HK Queue Manager subsystem driver[1] tries > to load a firmware from initramfs during boot. Sometimes loading of this > firmware fails with error ETXTBSY. Digging a bit more observed that > deny_write_access() is returning ETXTBSY as inode->i_writecount is > 0 > for that file. This is because Unpacking initramfs does a > get_write_access(from open) but hasn't done put_write_access(from fput) > as it hasn't been scheduled yet. > > [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/soc/ti/knav_qmss_queue.c > > init/initramfs.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/init/initramfs.c b/init/initramfs.c > index b32ad7d97ac9..981f286c1d16 100644 > --- a/init/initramfs.c > +++ b/init/initramfs.c > @@ -18,6 +18,7 @@ > #include > #include > #include > +#include > > static ssize_t __init xwrite(int fd, const char *p, size_t count) > { > @@ -647,6 +648,7 @@ static int __init populate_rootfs(void) > printk(KERN_EMERG "Initramfs unpacking failed: %s\n", err); > free_initrd(); > #endif > + flush_delayed_fput(); > /* > * Try loading default modules from initramfs. This gives > * us a chance to load before device_initcalls. > Not sure who else to cc here, get_maintainer.pl gives only LKML. Are there any comments on this patch? Thanks and regards, Lokesh