Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-parisc@vger.kernel.org, Helge Deller <deller@gmx.de>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	John David Anglin <dave.anglin@bell.net>,
	Randolph Chung <randolph@tausq.org>
Subject: Re: [PATCH] parisc: Add initial vDSO support
Date: Sat, 29 Jan 2022 15:55:23 +0100	[thread overview]
Message-ID: <11912593.O9o76ZdvQC@eto.sf-tec.de> (raw)
In-Reply-To: <20220129110342.50853-1-deller@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]

Am Samstag, 29. Januar 2022, 12:03:42 CET schrieb Helge Deller:
> Add minimal vDSO support, which provides the signal trampoline helpers, but
> none of the userspace syscall helpers like time functions.
> 
> The big benefit of this vDSO implementation is, that we now don't need an
> executeable stack any longer. PA-RISC is one of the last architectures where
> an executeable stack was needed in oder to implement the signal trampolines
> by putting assembly instructions on the stack which then gets executed.
> With this implementation the kernel will utilize the assembler statements
> in the vDSO page which is mapped into each userspace application instead
> and just put the pointers to the signal information on the stack.
> By dropping the need for executable stacks we now avoid running into issues
> with various applications in Debian which nowadays want non-executable
> stacks for security reasons. Additionally, alternative stacks are supported
> better as well.
> 
> This code is based on an initial implementation by Randolph Chung from 2006:
> https://lore.kernel.org/linux-parisc/4544A34A.6080700@tausq.org/
> 
> I did the porting and lifted the code to current code base. Dave fixed the
> unwind code so that gdb and glibc are able to backtrace through the code. An
> additional patch to gdb will be pushed upstream by Dave.

There are a few extra newlines in the first few files which you may or may not 
want to remove.

OTOH I would split out the change to mm_context_t into it's own patch, without 
adding the vdso_base there. This would reduce the overall size of the actual 
vdso patch and eases review.

Eike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2022-01-29 14:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 11:03 [PATCH] parisc: Add initial vDSO support Helge Deller
2022-01-29 14:55 ` Rolf Eike Beer [this message]
2022-01-29 16:42   ` Helge Deller

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=11912593.O9o76ZdvQC@eto.sf-tec.de \
    --to=eike-kernel@sf-tec.de \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dave.anglin@bell.net \
    --cc=deller@gmx.de \
    --cc=linux-parisc@vger.kernel.org \
    --cc=randolph@tausq.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