> > Found this will debugging some random memory corruptions that happen
> > when CONFIG_PROVE_LOCKING and CONFIG_PROFILE_LIKELY are both on.
> > Switching both off or having only one of them on seems to work.
>
> previously i had some weirdnesses with PROFILE_LIKELY too, they were
> caused by it generating cross-calls from within lockdep. Do the
> corruptions go away if you remove all likely() and unlikely() markings
> from kernel/lockdep.c?
No, unfortunately that doesn't help. I'm also wondering why the profile
patch contains this:
+ if (ret)
+ likeliness->count[1]++;
+ else
+ likeliness->count[0]++;
This isn't smp safe. Is that on purpose or a bug?
-
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]
