From: Arnd Bergmann <arnd@arndb.de>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: situation with signals
Date: Fri, 24 Sep 2010 15:33:23 +0200 [thread overview]
Message-ID: <201009241533.23331.arnd@arndb.de> (raw)
In-Reply-To: <20100923221141.GK19804@ZenIV.linux.org.uk>
On Friday 24 September 2010, Al Viro wrote:
> There are several interesting issues in arch/*/*/*signal* (besides
> shoggoths starting to show up when one reads that code) and I'd been crawling
> through that area for the last few weeks. Here are more or less common
> issues; there are really arch-specific bugs (e.g. roothole on frv that
> used to allow reading kernel memory by setting the right sa_handler), but
> that's a separate story.
I still plan to make a counterpart to the asm-generic headers with an
example architecture that new architectures can copy from. Signal handling
is one of the areas that I have very limited understanding of. Did you
encounter any architecture that basically gets signal handling right and that
can serve as a positive example to others?
arch/tile/kernel/signal.c was the last one that got merged and I tried
to direct the maintainer in the right direction as much as I could, but
there are a lot of things I didn't know about.
Arnd
next prev parent reply other threads:[~2010-09-24 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 22:11 situation with signals Al Viro
2010-09-24 13:33 ` Arnd Bergmann [this message]
[not found] ` <9lYpY1#WLHA.1516@exchange1.tad.internal.tilera.com>
2010-10-27 21:02 ` Chris Metcalf
2010-10-27 21:02 ` Chris Metcalf
2010-10-27 21:37 ` Al Viro
2010-10-27 22:51 ` Chris Metcalf
2010-10-27 23:30 ` Al Viro
2010-10-28 19:47 ` [PATCH] arch/tile: don't allow user code to set the PL via ptrace or signal return Chris Metcalf
2010-10-28 19:47 ` Chris Metcalf
2010-10-28 19:03 ` [PATCH] arch/tile: correct double syscall restart for nested signals Chris Metcalf
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=201009241533.23331.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).