Re: [PATCH] fix send_sigqueue() vs thread exit race

Thomas Gleixner wrote:
> 
>  arm timer
>  exit
>  timer event

I think there is another bug here.

CPU_0					CPU_1

release_task:				posix_timer_fn:
	write_lock(tasklist);			lock(timer->it_lock);

	exit_timers:				send_sigxxx();
		lock(timer->it_lock)			read_lock(tasklist);
				
Deadlock.

Dear cc-list, what do you think?

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] fix send_sigqueue() vs thread exit race
    • From: Thomas Gleixner <[email protected]>

• References:
  • 2.6.13-rc6-rt9
    • From: Ingo Molnar <[email protected]>
  • [PATCH 2.6.13-rc6-rt9] PI aware dynamic priority adjustment
    • From: Thomas Gleixner <[email protected]>
  • [PATCH] fix send_sigqueue() vs thread exit race
    • From: Oleg Nesterov <[email protected]>
  • Re: [PATCH] fix send_sigqueue() vs thread exit race
    • From: Thomas Gleixner <[email protected]>

• Prev by Date: Re: [PATCH] fix send_sigqueue() vs thread exit race
• Next by Date: Re: CONFIG_PRINTK_TIME woes
• Previous by thread: Re: [PATCH] fix send_sigqueue() vs thread exit race
• Next by thread: Re: [PATCH] fix send_sigqueue() vs thread exit race
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]