Re: [PATCH v2] initramfs: finish fput() before accessing any binary from initramfs

2017-02-01 Thread Lokesh Vutla
On Wednesday 01 February 2017 05:58 PM, Al Viro wrote: > On Tue, Jan 24, 2017 at 11:06:36AM +0530, 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

Re: [PATCH v2] initramfs: finish fput() before accessing any binary from initramfs

2017-02-01 Thread Al Viro
On Tue, Jan 24, 2017 at 11:06:36AM +0530, 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

Re: [PATCH v2] initramfs: finish fput() before accessing any binary from initramfs

2017-02-01 Thread Lokesh Vutla
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 bo

[PATCH v2] initramfs: finish fput() before accessing any binary from initramfs

2017-01-23 Thread Lokesh Vutla
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