Ashok Raj <[email protected]> wrote:
>
> Now we leave a trace in current->flags indicating current thread already
> is under cpucontrol lock held, so we dont attempt to do this another time.
>
> ..
> +#define PF_HOTPLUG_CPU 0x01000000 /* Currently performing CPU hotplug */
>
It's still hacky - I mean, we could use this trick to avoid recursion onto
any lock in the kernel whenever we get ourselves into a mess. We'd gain an
awful lot of PF_* flags.
So we should still view this as a temporary fix.
I don't think I've seen an analysis of the actual deadlock yet. Are you
able to provide a stack trace of the offending callpath?
-
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/
[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]
