>>>>> "Nikolay" == Nikolay Borisov <ker...@kyup.com> writes:
Nikolay> On 10/08/2015 05:34 PM, John Stoffel wrote: >> Great bug report, but you're missing the info on which kernel >> you're Nikolay> This is on 3.12.47 (self compiled). It was evident on my Nikolay> initial post, but I did forget to mention that in the Nikolay> reply. Also, I suspect even current kernel are susceptible to Nikolay> this since the locking in question hasn't changed. Hi Nikolay, must have missed it. I looked quickly, but didn't find it. Since it's such an older kernel release, it might be best if you upgrade to the latest version and try to re-create the lock if at all possible. What kind of workload are you running on there? And if you have more details on the hardware, that might help as well. John -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
