All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] syscall restart issue with SIGINFO handlers
Date: Wed, 31 Mar 2010 19:43:34 +0200	[thread overview]
Message-ID: <4BB389C6.7040902@domain.hid> (raw)
In-Reply-To: <4BB3861F.4070303@domain.hid>

Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
>> Hi Gilles,
>>
>> here is a case so far uncaught by Xenomai syscall restart code:
>>
>> #include <pthread.h>
>> #include <stdio.h>
>> #include <signal.h>
>> #include <unistd.h>
>> #include <sys/mman.h>
>> #include <native/task.h>
>> #include <native/mutex.h>
>>
>> RT_MUTEX mutex;
>> pthread_t pthread;
>>
>> void sighand1(int sig)
>> {
>> 	printf("signal 1: %d\n", sig);
>> }
>>
>> void sighand2(int sig, siginfo_t *si, void *context)
>> {
>> 	printf("signal 2: %d\n", sig);
>> }
>>
>> void thread(void *arg)
>> {
>> 	int res1, res2;
>>
>> 	pthread = pthread_self();
>>
>> 	res1 = rt_mutex_acquire(&mutex, TM_INFINITE);
>>
>> 	res2 = rt_mutex_release(&mutex);
>>
>> 	printf("res = %d / %d\n", res1, res2);
>> }
>>
>> int main()
>> {
>> 	struct sigaction sa;
>> 	RT_TASK task_main, task;
>>
>> 	mlockall(MCL_CURRENT|MCL_FUTURE);
>>
>> 	signal(SIGUSR1, sighand1);
>>
>> 	sigemptyset(&sa.sa_mask);
>> 	sa.sa_sigaction = sighand2;
>> 	sa.sa_flags = SA_SIGINFO;
>> 	sigaction(SIGUSR2, &sa, NULL);
>>
>> 	rt_task_shadow(&task_main, "main", 1, 0);
>>
>> 	rt_mutex_create(&mutex, "mutex");
>> 	rt_mutex_acquire(&mutex, TM_INFINITE);
>>
>> 	rt_task_spawn(&task, "thread", 0, 2, 0, thread, 0);
>>
>> 	sleep(1);
>> 	pthread_kill(pthread, SIGUSR1);
>>
>> 	sleep(1);
>> 	pthread_kill(pthread, SIGUSR2);
>>
>> 	rt_mutex_release(&mutex);
>>
>> 	rt_task_delete(&task);
>>
>> 	return 0;
>> }
>>
>>
>> Sending SIGUSR2 will make the blocked thread see -EINTR as result of its
>> rt_mutex acquire. Some different path must be taken by libc when
>> delivering SA_SIGINFO signals and returning to the application. Can you
>> confirm this?
> 
> If you want syscalls to be automatically restarted, you should pass the
> SA_RESTART flag to sigaction. It is unrelated to SA_SIGINFO unless I
> missed something.

Oh, indeed, that works. Should explain the issue in the field, my
colleagues likely missed that too.

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux


      reply	other threads:[~2010-03-31 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31 17:23 [Xenomai-core] syscall restart issue with SIGINFO handlers Jan Kiszka
2010-03-31 17:27 ` Gilles Chanteperdrix
2010-03-31 17:43   ` Jan Kiszka [this message]

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=4BB389C6.7040902@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=xenomai@xenomai.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.