From: WANG Cong <xiyou.wangcong@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [patch] UML kernels on {i386,x86_64} produce bad coredumps
Date: Wed, 26 Jan 2011 04:29:43 +0000 (UTC) [thread overview]
Message-ID: <iho7vn$kmn$2@dough.gmane.org> (raw)
In-Reply-To: 20110125231433.F2408190C3A@elbrus2.mtv.corp.google.com
On Tue, 25 Jan 2011 15:14:33 -0800, Paul Pluzhnikov wrote:
...
> Examining the core shows that NT_PRSTATUS notes for all threads other
> than the one that crashed are zeroed out.
>
> I believe this is happening because neither ELF_CORE_COPY_TASK_REGS nor
> task_pt_regs are defined under ARCH=um, and so elf_core_copy_task_regs()
> becomes a no-op.
I think this was missed due to some cleanups of the core elf
change, UML is one of the part overlooked by people. :-/
>
> Attached patch fixes this for SUBARCH={x86_64,i386}.
>
> Thanks,
> --
> Paul Pluzhnikov
>
> P.S. Google has blanket FSF copyright assignment.
>
>
> Signed-off-by: Paul Pluzhnikov <ppluzhnikov@google.com>
>
Acked-by: WANG Cong <xiyou.wangcong@gmail.com>
Thanks.
prev parent reply other threads:[~2011-01-26 4:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 23:14 [patch] UML kernels on {i386,x86_64} produce bad coredumps Paul Pluzhnikov
2011-01-26 4:29 ` WANG Cong [this message]
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='iho7vn$kmn$2@dough.gmane.org' \
--to=xiyou.wangcong@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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