"Paul E. McKenney" wrote: > > The other thing to think through is tkill on a thread/process while it > is being created. I believe that this is OK, since thread-specific > kill must target a specific thread, so does not do the traversal. > Also, tkill was not converted to use rcu_read_lock yet, it still takes tasklist_lock, so I think it is safe. Oleg. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH 2/2] fix kill_proc_info() vs fork() theoretical race
- From: "Paul E. McKenney" <[email protected]>
- Re: [PATCH 2/2] fix kill_proc_info() vs fork() theoretical race
- References:
- [PATCH] fix kill_proc_info() vs copy_process() race
- From: Oleg Nesterov <[email protected]>
- Re: [PATCH] fix kill_proc_info() vs copy_process() race
- From: "Paul E. McKenney" <[email protected]>
- Re: [PATCH] fix kill_proc_info() vs copy_process() race
- From: Oleg Nesterov <[email protected]>
- [PATCH 2/2] fix kill_proc_info() vs fork() theoretical race
- From: Oleg Nesterov <[email protected]>
- Re: [PATCH 2/2] fix kill_proc_info() vs fork() theoretical race
- From: "Paul E. McKenney" <[email protected]>
- Re: [PATCH 2/2] fix kill_proc_info() vs fork() theoretical race
- From: Oleg Nesterov <[email protected]>
- Re: [PATCH 2/2] fix kill_proc_info() vs fork() theoretical race
- From: "Paul E. McKenney" <[email protected]>
- [PATCH] fix kill_proc_info() vs copy_process() race
- Prev by Date: Re: [PATCH 1/2] fix kill_proc_info() vs CLONE_THREAD race
- Next by Date: Re: Linux 2.6.16-rc3
- Previous by thread: Re: [PATCH 2/2] fix kill_proc_info() vs fork() theoretical race
- Next by thread: Re: [PATCH 2/2] fix kill_proc_info() vs fork() theoretical race
- Index(es):
 |