linux-kernel - Re: [braindump][RFC] signals and syscall restarts (Re: [PATCH v2 19/44] metag: Signal handling)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20121215170741.GU4939@ZenIV.linux.org.uk>
Date:	Sat, 15 Dec 2012 17:07:41 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Jonas Bonn <jonas.bonn@...il.com>
Cc:	James Hogan <james.hogan@...tec.com>,
	"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Arnd Bergmann <arnd@...db.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [braindump][RFC] signals and syscall restarts (Re: [PATCH v2
 19/44] metag: Signal handling)

On Sat, Dec 15, 2012 at 05:26:30PM +0100, Jonas Bonn wrote:

> That said, let me point again to the series I posted for review a year
> ago that attempts to make the restart logic more generic:
> 
> https://lkml.org/lkml/2011/10/23/80
> 
> The entires patch series, which doesn't necessarily even apply to
> Linux master anymore due to other changes along the way, can be found
> at:
> 
> git://openrisc.net/~jonas/linux  ('signal-arch' branch)
> 
> Commit 4aa1797d978fe2d45ececceee535257e19374df8 is the interesting one there.
> 
> Al, what do you think?

In principle that's a nice cleanup, but...  For one thing, I really do not
believe that we should be returning to userland for handlerless restarts.
At all.  In that respect s390 and arm do it right.  Moreover, the loop calling
do_notify_resume() is better off in C (see e.g. alpha and arm for examples of
that approach).

Another thing is interplay with ptrace ;-/  And ptrace ABI is pretty much
"whatever gdb and its ilk happen to rely upon" - it's not formalized at
all and by now it's too late for existing ports.  Worse, we get to keep it
working as is; old binaries shall not be broken.

Hell knows...  ptrace vs. signals is a thing of horror, indeed - I had a damn
good reason for not including it into this braindump.  Note that there are
several aspects of behaviour that vary between the architectures:
	* get_signal_to_deliver() is a chance for tracer to play with our
state; what instruction pointer value should it see in case of possible
restart?
	* Does the change of instruction pointer done by tracer cancel
restart?  Or is there some other way for tracer to signal the need of
such cancel?
	* Does the change of syscall return value done by tracer affect
(or cancel) the restart?
And that's just for starters - I'm leaving aside the unholy mess around
single-stepping vs. signals.  The question here is not just "what behaviour
would make sense if we designed it from scratch", it's "what behaviour is
demonstrated by this architecture".  gdb is chock-full of arch-dependent
workarounds and yes, we need to keep that working.  Moreover, gdb isn't
the only thing tied to that crap.

	What we need is a decent review of what's in there for all
architectures.  And that'll take cooperation from maintainers -
it's far too easy to miss things on 3rd-party review in that area ;-/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/