Re: qemu:metag image runtime failure in -next due to 'kthread: allow to cancel kthread work'

From: James Hogan
Date: Tue Sep 27 2016 - 06:19:42 EST

On 27 September 2016 11:12:36 BST, Petr Mladek <pmladek@xxxxxxxx> wrote:
>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
>> > > the ELF, i.e. the total MemSiz's, not taking into account the
>> > > gap in between, so it puts them at 0x40377348.
>> >
>> > QEMU meta-v1.3.1 branch updated at:
>> >
>> >
>> > 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

Yes, that patch is sufficient.

>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.

Agreed, it altered the alignment of the sections enough to trigger linker generating multiple load program headers with a gap in between which confused qemu.