From mboxrd@z Thu Jan 1 00:00:00 1970 From: Petr Mladek Subject: Re: qemu:metag image runtime failure in -next due to 'kthread: allow to cancel kthread work' Date: Tue, 27 Sep 2016 12:12:36 +0200 Message-ID: <20160927101236.GB26796@pathway.suse.cz> References: <20160916203819.GA29767@roeck-us.net> <20160916212720.GA18931@jhogan-linux.le.imgtec.org> <20160916213718.GA32384@roeck-us.net> <20160916233249.GB18931@jhogan-linux.le.imgtec.org> <20160919145529.GK18931@jhogan-linux.le.imgtec.org> <20160919154509.GA24003@roeck-us.net> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20160919154509.GA24003-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org> Sender: linux-metag-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Guenter Roeck , Andrew Morton Cc: James Hogan , linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Tejun Heo , linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Ingo Molnar , kernel-hardening-ZwoEplunGu1jrUoiu81ncdBPR1lH4CV8@public.gmane.org, Kees Cook On Mon 2016-09-19 08:45:09, Guenter Roeck wrote: > On Mon, Sep 19, 2016 at 03:55:29PM +0100, James Hogan wrote: > > On Sat, Sep 17, 2016 at 12:32:49AM +0100, James Hogan wrote: > > > Here this version of QEMU puts the args at where it thinks the end of > > > the loaded image is, which is based on the number of bytes copied from > > > the ELF, i.e. the total MemSiz's, not taking into account the alignment > > > gap in between, so it puts them at 0x40377348. > > > > QEMU meta-v1.3.1 branch updated at: > > https://github.com/img-meta/qemu.git > > > > Hopefully that'll fix it for you Guenter. > > > Confirmed fixed. Could you please confirm that the boot problem has been fixed on the qemu side? I guess that it is https://github.com/img-meta/qemu/commit/0a2402860228198ae2729048f1de05aeedb7d642 Could Andrew enable all the kthread worker API improvements in -mm tree again? I think that kthread worker patch has been an innocent victim. It added some functions that were not used anywhere. I think that it has triggered the boot problem just by chance. Best Regards, Petr