linux-kernel - Re: problem with signal delivery SIGCHLD

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1166598615.1614.55.camel@Homer.simpson.net>
Date:	Wed, 20 Dec 2006 08:10:15 +0100
From:	Mike Galbraith <efault@....de>
To:	Nicholas Mc Guire <der.herr@...r.at>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: problem with signal delivery SIGCHLD

On Mon, 2006-12-18 at 20:05 +0100, Nicholas Mc Guire wrote:
> 
> Hi !
> 
>   I have a phenomena that I don't quite understand. gdbserver forks and 
> after setting ptrace (PTRACE_TRACEME, 0, 0, 0); it then execv 
> (program, allargs); when this child process hits ptrace_stoped (breakpoint
> it does the following in kernel space:
> 
> pid 1242 = child process
> pid 1241 = gdbserver
> pid 0    = kernel
> pid -1   = interrupt
>                                      pid
>           1        559          5    1242 ptrace_stop
>           3          6          2    1242 |  do_notify_parent_cldstop
>           4          3          2    1242 |  |  __group_send_sig_info
>           5          1          1    1242 |  |  |  handle_stop_signal
>           7          0          0    1242 |  |  |  sig_ignored
>           8          1          0    1242 |  |  __wake_up_sync
>           8          1          1    1242 |  |  |  __wake_up_common
>          10        547        541    1242 |  schedule
>          10          2          2    1242 |  |  profile_hit
>          13          1          1    1242 |  |  sched_clock
>          15          1          0    1242 |  |  deactivate_task
>          15          1          1    1242 |  |  |  dequeue_task
>          19          2          2       0 |  |  __switch_to
> ----------- !!!! start --------------
>          24        574        574       0 default_idle
> ----------- $$$$ end ----------------
> ----------- //// start --------------
>         780         41         12       0 do_IRQ
>         780         29          2      -1 /  __do_IRQ
>         ...
>         807          2          2      -1 /  /  /  enable_8259A_irq
> ----------- //// end ----------------
> ----------- {{{{ start --------------
>         810         11          0       0 do_softirq
>         ...
>         820          0          0      -1 {  {  {  preempt_schedule
> ----------- {{{{ end ----------------
> ----------- %%%% start --------------
>         822        358          1       0 preempt_schedule_irq
>         ...
>         827          1          1    1241 %  %  __switch_to
> ----------- %%%% end ----------------
>         829          1          1    1241 (  (  (  del_timer
> ----------- (((( end ----------------
> ----------- ]]]] start --------------
>         837          8          2    1241 sys_waitpid
> 
> So basically child signals -> delayed to next tick -> parent wakes up.

Hm.  What does the trace of gdbserver look like prior to the clild doing
do_notify_parent_cldstop()?  Sleeping someplace other than wait4?

	-Mike

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/