Re: [PATCH 3/2] fix flush_workqueue() vs CPU_DEAD race

On Wed, Jan 03, 2007 at 07:34:59PM +0530, Gautham R Shenoy wrote:
> 
> > handle-cpu_lock_acquire-and-cpu_lock_release-in-workqueue_cpu_callback.patch
> 
> Again, this one ensures that workqueue_mutex is taken/released on
> CPU_LOCK_ACQUIRE/CPU_LOCK_RELEASE events in the cpuhotplug callback
> function. So this one is required, unless it conflicts with what Oleg
> has posted. Will check that out tonite.

We would still be needing this patch as it's complementing what Oleg has
posted.

Thanks and Regards
gautham.
-- 
Gautham R Shenoy
Linux Technology Center
IBM India.
"Freedom comes with a price tag of responsibility, which is still a bargain,
because Freedom is priceless!"
-
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 3/2] fix flush_workqueue() vs CPU_DEAD race
    • From: Oleg Nesterov <[email protected]>

• References:
  • Re: [PATCH 3/2] fix flush_workqueue() vs CPU_DEAD race
    • From: Andrew Morton <[email protected]>
  • Re: [PATCH 3/2] fix flush_workqueue() vs CPU_DEAD race
    • From: Gautham R Shenoy <[email protected]>

• Prev by Date: Re: [PATCH v4 01/13] Linux RDMA Core Changes
• Next by Date: Re: [PATCH v4 01/13] Linux RDMA Core Changes
• Previous by thread: Re: [PATCH 3/2] fix flush_workqueue() vs CPU_DEAD race
• Next by thread: Re: [PATCH 3/2] fix flush_workqueue() vs CPU_DEAD race
• Index(es):
  • Date
  • Thread

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