All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: David Howells <dhowells@redhat.com>,
	Russell King - ARM Linux admin <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PULL REQUEST v2] FDPIC ELF support for ARM
Date: Tue, 9 Jun 2020 05:19:39 +0100	[thread overview]
Message-ID: <20200609041939.GQ23230@ZenIV.linux.org.uk> (raw)
In-Reply-To: <nycvar.YSQ.7.77.849.2006082137050.1353413@knanqh.ubzr>

On Mon, Jun 08, 2020 at 11:48:27PM -0400, Nicolas Pitre wrote:

> I suspect riscv will end up in the same situation when they upstream 
> their fdpic support.

FWIW, one thing that needs to be done is switching fdpic to use
of regset, a-la normal elf coredumps on the same arm.  I really want
to kill the sodding elf_core_copy_task_fpregs(), dump_fpu(),
etc.

Right now that crap is used by
	elf coredump on alpha c6x csky h8300 m68k microblaze nds32 um unicore32
	fdpic coredump on arm sh/nommu and c6x

Out of those only alpha, m68k, microblaze, um and unicore32 lack
regset - everything else (including all users of fdpic) have working ones.
And it's not at all hard to add the damn thing to those 5 architectures,
killing quite bit of code in binfmt_elf.c, as well as in arch/*

Note, BTW, that fdpic coredumps on arm currently have fucked FPU
for all but the main thread - arm has
int dump_fpu (struct pt_regs *regs, struct user_fp *fp)
{
        struct thread_info *thread = current_thread_info();
        int used_math = thread->used_cp[1] | thread->used_cp[2];

        if (used_math)
                memcpy(fp, &thread->fpstate.soft, sizeof (*fp));

        return used_math != 0;
}  
which obviously duplicates the contents of FP registers of the coredumping
thread into the NT_PRFPREG section for each thread...

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-06-09  4:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30  3:16 [PULL REQUEST v2] FDPIC ELF support for ARM Nicolas Pitre
2017-09-19 21:14 ` Nicolas Pitre
2020-06-08 22:47 ` Russell King - ARM Linux admin
2020-06-09  3:48   ` Nicolas Pitre
2020-06-09  4:19     ` Al Viro [this message]
2020-06-09  8:06     ` David Howells

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=20200609041939.GQ23230@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=dhowells@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=nico@fluxnic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.