| commit | b413921e53550e92d6cf764f5e4c837b8d5f5df1 | |
| author | Rusty Russell <rusty@rustcorp.com.au> | |
| Fri, 28 Aug 2009 02:38:47 +0000 (28 12:08 +0930) | ||
| committer | Karolin Seeger <kseeger@samba.org> | |
| Wed, 9 Sep 2009 10:45:07 +0000 (9 12:45 +0200) | ||
| tree | 6c9935f02174f189c462b0ba36f3ef9c1ab22b64 | treesnapshot (tar.gz zip) |
| parent | c1011b3a21298fcde7a81a23412b3e2450e15942 | commitdiff |
lib/tevent: handle tevent_common_add_signal on different event contexts.
I don't know if this is a problem in real life.
The code assumes there's only one tevent_context; all signals will notify
the first event context. That's counter-intuitive if you ever use more
than one, and there's nothing else in this code which prevents it AFAICT.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
(cherry picked from commit be4ac227842530d484659f2db683453366326d8b)
(cherry picked from commit 792ab5c34a20bd2b292b642dc96cae62e5ad1ce0)
I don't know if this is a problem in real life.
The code assumes there's only one tevent_context; all signals will notify
the first event context. That's counter-intuitive if you ever use more
than one, and there's nothing else in this code which prevents it AFAICT.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
(cherry picked from commit be4ac227842530d484659f2db683453366326d8b)
(cherry picked from commit 792ab5c34a20bd2b292b642dc96cae62e5ad1ce0)
| lib/tevent/tevent_internal.h | diffblobblamehistory | |
| lib/tevent/tevent_signal.c | diffblobblamehistory |