From: Petr Mladek <pmladek@suse.com>
To: Guenter Roeck <linux@roeck-us.net>,
Andrew Morton <akpm@linux-foundation.org>
Cc: James Hogan <james.hogan@imgtec.com>,
linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
linux-metag@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
kernel-hardening@lists.openwall.com,
Kees Cook <keescook@chromium.org>
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 [thread overview]
Message-ID: <20160927101236.GB26796@pathway.suse.cz> (raw)
In-Reply-To: <20160919154509.GA24003@roeck-us.net>
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
next prev parent reply other threads:[~2016-09-27 10:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 20:38 Guenter Roeck
2016-09-16 21:27 ` James Hogan
2016-09-16 21:37 ` Guenter Roeck
2016-09-16 23:32 ` James Hogan
2016-09-17 2:58 ` Kees Cook
2016-09-19 13:59 ` James Hogan
2016-09-19 19:53 ` Kees Cook
2016-09-19 21:37 ` James Hogan
2016-09-19 21:51 ` Kees Cook
2016-09-19 22:57 ` James Hogan
2016-09-19 23:19 ` Kees Cook
2016-09-19 14:55 ` James Hogan
2016-09-19 15:45 ` Guenter Roeck
2016-09-27 10:12 ` Petr Mladek [this message]
2016-09-27 10:19 ` James Hogan
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=20160927101236.GB26796@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=james.hogan@imgtec.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mingo@kernel.org \
--cc=tj@kernel.org \
/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®