On Wed, Jan 31, 2018 at 9:21 AM, Heiko Carstens <heiko.carstens@xxxxxxxxxx> wrote: > On Wed, Jan 31, 2018 at 08:41:39AM +0000, Eugene Syromyatnikov wrote: >> On Wed, Jan 31, 2018 at 7:20 AM, Heiko Carstens >> <heiko.carstens@xxxxxxxxxx> wrote: >> > @@ -85,6 +91,12 @@ The run-time instrumentation facility is available beginning with System z EC12. >> > Glibc does not provide a wrapper for this system call, use >> > .BR syscall (2) >> > to call it. >> > +.PP >> > +Support for signalling was removed with Linux 4.4. With Linux 4.4 >> > +also the check if >> > +.IR signum >> > +is a valid real-time signal was removed. For backwards compatibility with old >> > +kernels it is recommended to pass a valid real-time signal number. >> I would recommend passing 0 instead, as passing non-zero signal number >> implies that the userspace process expects to receive this signal in >> the future in case of aforementioned events, and this will not happen >> on Linux 4.4 onwards. > > Passing 0 as signum is not backwards compatible, since that will result in > an error with old kernels. > Oh, I see, sorry, for some reason I thought that passing 0 was equivalent to the current behaviour (no signal is sent), but after checking the code again I see that it is not the case. -- Eugene Syromyatnikov mailto:evgsyr@xxxxxxxxx xmpp:esyr@jabber.{ru|org} -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
