Re: [PATCH] flush_cpu_workqueue: don't flush an empty ->worklist

On Tue, Jan 09, 2007 at 01:51:52AM -0800, Andrew Morton wrote:
> > This thread makes absolutely -no- calls to try_to_freeze() in its lifetime.
> 
> Looks like a bug to me.  powerpc does appear to try to support the freezer.
> 
> > 1. Does this mean that the thread can't be frozen? (lets say that the
> >    thread's PF_NOFREEZE is not set)
> 
> yup.  I'd expect the freeze_processes() call would fail if this thread is
> running.

ok.

> 
> >    AFAICS it can still be frozen by sending it a signal and have the signal
> >    delivery code call try_to_freeze() ..
> 
> kernel threads don't take signals in the same manner as userspace.  A
> kernel thread needs to explicitly poll, via
> 
> 	if (signal_pending(current))
> 		do_something()

Thanks for the education! I feel much better about the use of process
freezer now ..

> > 2. If the thread can be frozen at any arbitrary point of its execution, then I
> >    dont see what prevents cpu_online_map from changing under the feet of rtasd
> >    thread,
> 
> It cannot.

Excellent ..

I just hope the latency of freeze_processes() is tolerable ..

-- 
Regards,
vatsa
-
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] flush_cpu_workqueue: don't flush an empty ->worklist
    • From: Andrew Morton <[email protected]>

• References:
  • Re: [PATCH] fix-flush_workqueue-vs-cpu_dead-race-update
    • From: Srivatsa Vaddagiri <[email protected]>
  • Re: [PATCH] fix-flush_workqueue-vs-cpu_dead-race-update
    • From: Andrew Morton <[email protected]>
  • Re: [PATCH] fix-flush_workqueue-vs-cpu_dead-race-update
    • From: Srivatsa Vaddagiri <[email protected]>
  • Re: [PATCH] fix-flush_workqueue-vs-cpu_dead-race-update
    • From: Andrew Morton <[email protected]>
  • [PATCH] flush_cpu_workqueue: don't flush an empty ->worklist
    • From: Oleg Nesterov <[email protected]>
  • Re: [PATCH] flush_cpu_workqueue: don't flush an empty ->worklist
    • From: Andrew Morton <[email protected]>
  • Re: [PATCH] flush_cpu_workqueue: don't flush an empty ->worklist
    • From: Srivatsa Vaddagiri <[email protected]>
  • Re: [PATCH] flush_cpu_workqueue: don't flush an empty ->worklist
    • From: Andrew Morton <[email protected]>
  • Re: [PATCH] flush_cpu_workqueue: don't flush an empty ->worklist
    • From: Srivatsa Vaddagiri <[email protected]>
  • Re: [PATCH] flush_cpu_workqueue: don't flush an empty ->worklist
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: bd_mount_mutex -> bd_mount_sem (was Re: xfs_file_ioctl / xfs_freeze: BUG: warning at kernel/mutex-debug.c:80/debug_mutex_unlock())
• Next by Date: Re: [PATCH - RFC] allow setting vm_dirty below 1% for large memory machines
• Previous by thread: Re: [PATCH] flush_cpu_workqueue: don't flush an empty ->worklist
• Next by thread: Re: [PATCH] flush_cpu_workqueue: don't flush an empty ->worklist
• 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]