* Dmitry Vyukov <dvyukov@xxxxxxxxxx> wrote: > > I've pushed these two out into tip:locking/core, future (re-)submissions should be > > based on that tree. > > Hi Ingo, > > It's still in my sight, but was preempted by other tasks. Also I am > somewhat scared by the amount of changes for the final plan. > > Thanks for taking these 2. That's a good start. Can you please also merge: > 68c1ed1fdb0a: kasan: Allow kasan_check_read/write() to accept pointers > to volatiles > It's small and harmless and will be needed anyway. Ok, I cherry-picked this one into tip:locking/core as well. > For the rest of the changes: will it be ok to just resolve the cmpxchg > macro mess (that caused the crash) and then rebase the current changes > on top of that? Or we need to do the full overhaul across all arches? > If we go with full overhaul, would somebody with more kernel expertise > be willing to do the overhaul? That's up to Thomas. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|