News for hackers. Stuff that matters.
Re:Should you be scared of Unix signals? by Qwertious on Tuesday June 14, 2016 @12:56AM (#11899874)
>The worst bugs and races were fixed up by the BSD folks and others, but the underlying concept is an unfortunate combination of "basically irredeemable", "indispensable" (you have to have some kind of "kernel tells you something has happened" API, and signals are what we got) and "insidious" (thanks to EINTR). I think they're a strong candidate for "worst design decision in unix".

Suppose you were to throw the whole thing out and write a good replacement (and backwards-compatibility be damned), what would it be like?

Re:Should you be scared of Unix signals? by pjc50 on Tuesday June 14, 2016 @04:54AM (#11900680)
Suppose you were to throw the whole thing out and write a good replacement (and backwards-compatibility be damned), what would it be like?

Steal the best bits from Windows NT, and improve the existing mechanisms.

Kill signals in their current form. Build a general-purpose notification mechanism consisting of a mutex and a message. Possibly allow a process to have more than one message queue (Windows makes this really, really easy).

All IO, networking and informational signals (SIGWINCH, SIGCHLD etc) then come as messages (these may have to be fixed size, but anything from a few words to a 4k page would do). select, poll etc are replaced by waiting on a mutex. You can put all your worker threads waiting on that mutex. A message arrives. The kernel wakes one waiting thread and gives it the message (via an atomic deque-or-block syscall). You don't have to do any O(n) processing to work out which socket it relates to as the kernel has helpfully put it in the message.

In the deluxe 4k page version, a 1500-byte ethernet frame arrives, is DMA'd into the top half of a page, the kernel inspects it and sets message headers to say where the data is, and hands it directly into the userspace of a waiting process.

The one downside of this is that UNIX pipe programs become slightly more complicated. Rather than just doing "while(read()) write()" you'd have to switch on the type of message recieved and implement your own abnormal exit functionality. This could probably be tidied away for you inside the standard library.

External process control mechanisms would have to be built for killing processes and suspend/resume.

Re:Should you be scared of Unix signals? by gpderetta on Tuesday June 14, 2016 @06:59AM (#11901121)
Unix already has a general notification mechanism in the form of poll and select, no need to add a new one. The problem is not all interesting events are not portably delivered via a file descriptor, but that can be more easily extended (as done by lot of unices, including linux) than coming up with a completely new primitive.

But some messages really must be delivered synchronously and can't normally be queued: SIGSEGV, SIGFPE, SIGBUS, etc. There is really no way around interrupts.

BTW mutexes are not for signaling. What you want for signaling in a queue are semaphores, events or condition variables (or even file descriptors, like eventfd).

Re:Should you be scared of Unix signals? by pjc50 on Tuesday June 14, 2016 @08:16AM (#11901486)
Well, the brief was to "throw the whole thing out", including select (which is bad) and poll (which is merely adequate).

The machine traps are interesting in that they should only be generated locally - there's no sensible case for injecting SIGSEGV into other processes. Arguably we should learn from Windows "structured exception handling" here. There are two sensible things to do with traps (other than sudden death): hand over to a callback of some kind (which should be told about the state of the stack), or turn into a language-native exception and throw that.

Re:Should you be scared of Unix signals? by gpderetta on Tuesday June 14, 2016 @08:25AM (#11901530)
Poll is perfectly fine for the very large majority of unix applications which do not need to scale to tens of thousands of sockets.

The handling over to callback is exactly what is done by unix signals. Converting to exceptions can be implemented on top of signal handlers, but note that even MS stopped mapping by default structured exceptions to language exception a while ago, at least in C++, as unwinding the stack, destroying state and potentially calling destructors is the last thing you want on a segmentation fault or other unexpected events.

Re:Should you be scared of Unix signals? by pjc50 on Tuesday June 14, 2016 @10:34AM (#11902238)
The handling over to callback is exactly what is done by unix signals

Not quite, there are quite a lot of restrictions on what you can do in a signal handler. It ought to be possible to design a callback mechanism without those restrictions. And a signal tells you nothing about its origin or what file descriptor / child process etc. it might relate to.

Re:Should you be scared of Unix signals? by gpderetta on Tuesday June 14, 2016 @10:59AM (#11902389)
I assume that by restrictions you are talking about the async signal safety; this is inherent on the 'interrupt' nature of signals as they can happen at any point in a program execution, there is really no way around that. It would be of course nice if more functions where async signal safe (especially malloc).

Regarding the lack metadata, I agreed else thread that messages that carry such data ought to be transported via an explicit message queue, not via signals.

Re:Should you be scared of Unix signals? by plorkyeran on Tuesday June 14, 2016 @02:51PM (#11904339)
The equivalent of SIGSEGV/SIGBUS on Mach is handled in basically the way he describes. On an access violation, it suspends the thread and delivers a message to the registered port. The thing listening on the port (in a different thread or even different process) receives the message, does whatever it needs to do, and then sends a response, after which the original thread is woken back up. From the perspective of the violating thread it was handled synchronously, but the actual implementation was an async message queue.
Re:Should you be scared of Unix signals? by gpderetta on Tuesday June 14, 2016 @03:56PM (#11904840)
It is not much better though. If it is another thread it has to work under the same async signal safety rules of a signal handler (the blocked thread might be holding an arbitrary mutex). If it is another process, there isn't a lot it can do.
Re:Should you be scared of Unix signals? by JdeBP on Tuesday June 14, 2016 @08:52AM (#11901657)
Now go and read https://news.ycombinator.com/item?id=11864211 . There are those who argue (at some length, q.v.) that "the best bits from Windows NT" are not to have readiness-oriented application designs in the first place.
Re:Should you be scared of Unix signals? by pjc50 on Tuesday June 14, 2016 @09:49AM (#11901983)
Any particular bit of that huge thread which I've already read? :P The bit under https://news.ycombinator.com/item?id=11866697 ?

I was thinking more along the lines of Windows "registered I/O" and Linux "netmap". 'trentnelson' argues for a distinction between readiness and asynchronous. I don't think the distinction needs to exist, and that in an ideal world the disk subsystem would be more like a kind of networking subsystem. If the request can't be satisfied from a RAM buffer, add it to the "outbound requests" list and return to the calling thread. When the corresponding reply eventually turns up from the disk, add it to the input queue of the process.

Re:Should you be scared of Unix signals? by JoshTriplett on Tuesday June 14, 2016 @06:09AM (#11900914)
> Suppose you were to throw the whole thing out and write a good replacement (and backwards-compatibility be damned), what would it be like?

Keep the "you can always kill or stop a process" provided by SIGKILL and SIGSTOP/SIGCONT, using dedicated system calls. Handle every other kind of message (from the kernel or otherwise) via file descriptors, similar to signalfd.

Re:Should you be scared of Unix signals? by JdeBP on Tuesday June 14, 2016 @09:01AM (#11901722)
That's two people so far who have mentioned signalfd here, without reference to what the headlined article has to say on the matter (which, ironically, amongst other things points to https://news.ycombinator.com/item?id=9564975 on Hacker News and what it, in its turn, points to).
Re:Should you be scared of Unix signals? by gmazza on Tuesday June 14, 2016 @06:48AM (#11901069)
(k)dbus is the most likely replacement here and systemd is a major vehicle for its adoption beyond DBus' current niche use in Gnome.
Re:Should you be scared of Unix signals? by ktRolster on Tuesday June 14, 2016 @03:58AM (#11900487)
systemd?

edit: Actually there are some fairly decent systems for IPC now, with the Mach kernel from CMU probably being the most popular example. Most systems with micro-kernels probably have something similar, and of course dbus is there, and Android intents.

I think Applescript deserves a mention here, because although it's a rather weird language, the IPC stuff is really really easy.

Re:Should you be scared of Unix signals? by rtpg on Tuesday June 14, 2016 @04:55AM (#11900686)
Considering that you can basically establish no invariants in the signals model, to me it sounds like a cooperative model is the way to go.

Have a way to poll for "outstanding" signals and deal with them accordingly, in some sort of queue (and the OS drops older messages or something, if they're important you'd deal with them).

The "freeze-the-world-and-do-this-thing-instead" model seems like the best way to introduce "my entire program is now broken"-style bugs. The OS deals with interrupts but the OS is also running by itself.

Re:Should you be scared of Unix signals? by jbarham on Tuesday June 14, 2016 @01:53AM (#11900066)
FWIW Plan 9 uses what it calls a "notification" mechanism: http://plan9.bell-labs.com/magic/man2html/2/notify
Re:Should you be scared of Unix signals? by adrianratnapala on Tuesday June 14, 2016 @02:57AM (#11900266)
While the "notification" system seems is cleaner than the signals system (and presumably avoids those races fixed by BSD) -- it does not seem fundamentally different.

If I am understanding that man page correctly, it does nothing at all to fix EINTR: "If the note interrupted an incomplete system call, that call returns an error (with error string interrupted) after the process resumes."

Re:Should you be scared of Unix signals? by nitwit005 on Tuesday June 14, 2016 @03:57AM (#11900483)
EINTR is only "needed" because of the situation where a call is made to a blocking system call like read, and a signal is received before it completes. It needs to cancel the blocking call so that it can run the signal handler.

If you get rid of signals, you wouldn't need EINTR. Even with signals, what people do 99% of the time is just retry the system call immediately. It would probably have been much better to have it do so automatically by default, avoiding exposing EINTR to most users.

Re:Should you be scared of Unix signals? by noselasd on Tuesday June 14, 2016 @08:55AM (#11901678)
EINTR is retried automatically if you use sigaction() and set the SA_RESTART flag.

If you use signal() instead of sigaction() it depends on your OS whether EINTR is automatically retried - never use signal().

(There's a few exceptions still - partial completed syscalls, e.g. a signal can cause read() to return partial data or sleep() to return before it should - neither case gives you EINTR though)

Re:Should you be scared of Unix signals? by adrianratnapala on Tuesday June 14, 2016 @05:41PM (#11905558)
Yes, but how does the Plan9 "notify" mechanism help with any of that? It seems to just be a tidied up version of signals, and therefore "needs" to do EINTR in much the same way as Unix.
Re:Should you be scared of Unix signals? by to3m on Tuesday June 14, 2016 @08:48AM (#11901634)
More on what EINTR is for: http://250bpm.com/blog:12
Re:Should you be scared of Unix signals? by reacweb on Tuesday June 14, 2016 @03:44AM (#11900419)
Maybe, the signal coming from another process should be handled in an independent thread (maybe created the first time a signal is raised). Something would still be needed to interrupt pending system calls.