mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Satoru Takeuchi <takeuchi_satoru.jp@fujitsu.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Ingo Molnar <mingo@elte.hu>, Roland McGrath <roland@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] signal: multithread program returns with wrong errno on receiving SIGSTOP
Date: Mon, 28 May 2007 18:58:50 +0900	[thread overview]
Message-ID: <87fy5hb76t.wl%takeuchi_satoru@jp.fujitsu.com> (raw)
In-Reply-To: <20070528070753.GA989@tv-sign.ru>

Hi Oleg,

At Mon, 28 May 2007 11:07:53 +0400,
Oleg Nesterov wrote:
> 
> Satoru Takeuchi wrote:
> >
> > I found a bug on signal subsystem. If there is some multithread program
> > and one of the thread is blocking on the system call, it returns with
> > wrong errno on receiving SIGSTOP and following SIGCONT.
> 
> It doesn't matter in this particular case, but in general it is good to
> report the kernel version as well.
> 
> > 1. issue the test program (attached on this mail) from term A.
> >
> >    $ ./mt-wrong-errno
> >
> > 2. send SIGSTOP to test program from term B.
> >
> >    $ ps a
> >    ...
> >     9685 pts/3    Sl+    0:00 ./mt-wrong-errno
> >     9688 pts/4    R+     0:00 ps a
> >    $ kill -STOP 9685
> >
> > 3. send SIGCONT to test program from term B.
> >
> >    $ kill -CONT 9685
> >
> > Expected Result
> > ===============
> >
> > `./mt-wrong-errno' restarts read syscall (and stop again by receiving
> > SIGTTIN).
> >
> > Actual Result
> > =============
> >
> > `./mt-wrong-errno' returns with wrong errno 512 means ERESTARTSYS.
> > The comment on include/linux/errno.h says "this errno should never be
> > seen by user program." So it's definitely a bug.
> 
> Wild guess,
> 
> 	drivers/char/n_tty.c:job_control()
> 
> 		kill_pgrp(task_pgrp(current), SIGTTIN, 1);
> 		return -ERESTARTSYS;
> 
> This is wrong. kill_pgrp()->__group_send_sig_info() sends SIGTTIN
> to the thread group, but can choose any sub-thread as a target for
> signal_wake_up().
> 
> This means we return ERESTARTSYS, but signal_pending() != true, bug.
> 
> Satoru, could you re-test with the untested patch below?

I tested this patch on my ia64 box and it works fine.

# Since I don't know anything about tty driver, I can't determine its
# adequacy immediately, sorry.

Satoru

> 
> Oleg.
> 
> --- t/drivers/char/n_tty.c~	2007-04-05 12:18:26.000000000 +0400
> +++ t/drivers/char/n_tty.c	2007-05-28 10:57:58.000000000 +0400
> @@ -1191,6 +1191,7 @@ static int job_control(struct tty_struct
>  			    is_current_pgrp_orphaned())
>  				return -EIO;
>  			kill_pgrp(task_pgrp(current), SIGTTIN, 1);
> +			set_thread_flag(TIF_SIGPENDING);
>  			return -ERESTARTSYS;
>  		}
>  	}
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2007-05-28  9:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-28  7:07 Oleg Nesterov
2007-05-28  9:58 ` Satoru Takeuchi [this message]
2007-05-28 10:13   ` Oleg Nesterov
2007-05-29  7:33 ` Roland McGrath
2007-05-29 19:22   ` Oleg Nesterov
2007-05-29 19:28     ` Roland McGrath
  -- strict thread matches above, loose matches on Subject: below --
2007-05-28  2:32 Satoru Takeuchi
2007-05-29  8:03 ` Andrew Morton
2007-05-29  8:04   ` Roland McGrath
2007-05-29  8:09   ` Satoru Takeuchi

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=87fy5hb76t.wl%takeuchi_satoru@jp.fujitsu.com \
    --to=takeuchi_satoru@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@tv-sign.ru \
    --cc=roland@redhat.com \
    --cc=takeuchi_satoru.jp@fujitsu.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®