From: Lokesh Vutla <lokeshvutla@ti.com>
To: Al Viro <viro@zeniv.linux.org.uk>, <linux-kernel@vger.kernel.org>,
<akpm@linux-foundation.org>
Cc: Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
Tero Kristo <t-kristo@ti.com>, Sekhar Nori <nsekhar@ti.com>,
Nishanth Menon <nm@ti.com>,
Muralidharan Karicheri <m-karicheri2@ti.com>
Subject: Re: [PATCH v2] initramfs: finish fput() before accessing any binary from initramfs
Date: Wed, 1 Feb 2017 14:54:46 +0530 [thread overview]
Message-ID: <f236f0b5-a1c4-2ed4-f41a-c50165f82f8a@ti.com> (raw)
In-Reply-To: <20170124053636.30121-1-lokeshvutla@ti.com>
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 <m-karicheri2@ti.com>
> Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
> ---
> 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 <linux/dirent.h>
> #include <linux/syscalls.h>
> #include <linux/utime.h>
> +#include <linux/file.h>
>
> 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
next prev parent reply other threads:[~2017-02-01 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 5:36 Lokesh Vutla
2017-02-01 9:24 ` Lokesh Vutla [this message]
2017-02-01 12:28 ` Al Viro
2017-02-01 13:45 ` Lokesh Vutla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f236f0b5-a1c4-2ed4-f41a-c50165f82f8a@ti.com \
--to=lokeshvutla@ti.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=t-kristo@ti.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®