From: James Hogan <james.hogan@imgtec.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Petr Mladek <pmladek@suse.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.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: Mon, 19 Sep 2016 15:55:29 +0100 [thread overview]
Message-ID: <20160919145529.GK18931@jhogan-linux.le.imgtec.org> (raw)
In-Reply-To: <20160916233249.GB18931@jhogan-linux.le.imgtec.org>
[-- Attachment #1: Type: text/plain, Size: 460 bytes --]
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.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-19 14:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 20:38 qemu:metag image runtime failure in -next due to 'kthread: allow to cancel kthread work' Guenter Roeck
[not found] ` <20160916203819.GA29767-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-09-16 21:27 ` James Hogan
[not found] ` <20160916212720.GA18931-4bYivNCBEGTR3KXKvIWQxtm+Uo4AYnCiHZ5vskTnxNA@public.gmane.org>
2016-09-16 21:37 ` Guenter Roeck
[not found] ` <20160916213718.GA32384-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-09-16 23:32 ` James Hogan
[not found] ` <20160916233249.GB18931-4bYivNCBEGTR3KXKvIWQxtm+Uo4AYnCiHZ5vskTnxNA@public.gmane.org>
2016-09-17 2:58 ` Kees Cook
[not found] ` <CAGXu5jLYGcSq0Sdm4Mmd12dAJUbiyrkU-+4RwbHoo=OpWfvNFg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-19 13:59 ` James Hogan
2016-09-19 19:53 ` Kees Cook
[not found] ` <CAGXu5jKxULh3+bUPa4vjqSW52xSEHWon9aLgKQ03Vv_DdZs3TA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-19 21:37 ` James Hogan
2016-09-19 21:51 ` Kees Cook
[not found] ` <CAGXu5jL6J3PNkxMi7UXj7jPVr6AQuHeMb2mygL4Y9thyi5M2TA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-19 22:57 ` James Hogan
[not found] ` <20160919225717.GO18931-4bYivNCBEGTR3KXKvIWQxtm+Uo4AYnCiHZ5vskTnxNA@public.gmane.org>
2016-09-19 23:19 ` Kees Cook
2016-09-19 14:55 ` James Hogan [this message]
[not found] ` <20160919145529.GK18931-4bYivNCBEGTR3KXKvIWQxtm+Uo4AYnCiHZ5vskTnxNA@public.gmane.org>
2016-09-19 15:45 ` Guenter Roeck
[not found] ` <20160919154509.GA24003-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2016-09-27 10:12 ` Petr Mladek
[not found] ` <20160927101236.GB26796-KsEp0d+Q8qECVLCxKZUutA@public.gmane.org>
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=20160919145529.GK18931@jhogan-linux.le.imgtec.org \
--to=james.hogan@imgtec.com \
--cc=akpm@linux-foundation.org \
--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=pmladek@suse.com \
--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