It had been fixed by Tejun already.
commit 477a3c33d1efa0342a74bd02da2e049191993e2c
Author: Tejun Heo <[email protected]>
Date: Tue Aug 31 10:54:35 2010 +0200
workqueue: fix GCWQ_DISASSOCIATED initialization
init_workqueues() incorrectly marks workqueues for all possible CPUs
associated. Combined with mayday_mask initialization bug, this can
make rescuers keep trying to bind to an offline gcwq indefinitely.
Fix init_workqueues() such that only online CPUs have their gcwqs have
GCWQ_DISASSOCIATED cleared.
----- "Rafael J. Wysocki" <[email protected]> wrote:
> This message has been generated automatically as a part of a summary
> report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.35. Please verify if it still should be listed and let the
> tracking team
> know (either way).
>
>
> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=17341
> Subject : kdump regression compared to v2.6.35
> Submitter : CAI Qian <[email protected]>
> Date : 2010-08-27 12:35 (25 days old)
> Message-ID :
> <2136707099.1405541282912500148.javamail.r...@zmail06.collab.prod.int.phx2.redhat.com>
> References : http://marc.info/?l=linux-kernel&m=128291252612135&w=2
> Handled-By : Tejun Heo <[email protected]>
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
