Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Mar 2016 19:20:57 +0000 (UTC)
From:      Dmitry Chagin <dchagin@FreeBSD.org>
To:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org
Subject:   svn commit: r296543 - head/sys/compat/linux
Message-ID:  <201603081920.u28JKvbM088851@repo.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: dchagin
Date: Tue Mar  8 19:20:57 2016
New Revision: 296543
URL: https://svnweb.freebsd.org/changeset/base/296543

Log:
  Put a commit message from r296502 about Linux alarm() system call
  behaviour to the source.
  
  Suggested by:	emaste@
  
  MFC after:	1 week

Modified:
  head/sys/compat/linux/linux_misc.c

Modified: head/sys/compat/linux/linux_misc.c
==============================================================================
--- head/sys/compat/linux/linux_misc.c	Tue Mar  8 19:08:55 2016	(r296542)
+++ head/sys/compat/linux/linux_misc.c	Tue Mar  8 19:20:57 2016	(r296543)
@@ -206,6 +206,11 @@ linux_alarm(struct thread *td, struct li
 	it.it_value.tv_usec = 0;
 	it.it_interval.tv_sec = 0;
 	it.it_interval.tv_usec = 0;
+	/*
+	 * According to POSIX and Linux implementation
+	 * the alarm() system call is always successfull.
+	 * Ignore errors and return 0 as a Linux do.
+	 */
 	kern_setitimer(td, ITIMER_REAL, &it, &old_it);
 	if (timevalisset(&old_it.it_value)) {
 		if (old_it.it_value.tv_usec != 0)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201603081920.u28JKvbM088851>