I will not be able to provide a reproducer of this immediately. If you
agree, please keep this open until I can have it or someone comes here
with his/her reproducer.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
Unfortunately, we don't have a repro case yet. Do you really need a
repro case to proceed this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1233175
Title:
Kernel panic : mempolicy pot
Hi Chris,
Does anyone of you have a repro case? Although the patch itself is
really straightforward, I don't have a reliable repro case of this race
unfortunately.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
Hi,
We also have experienced this issue with 3.2.0-57-generic. Thanks to the
core dump analysis by Louis Bouchard, I could notice that accessing
current->mempolicy in interrupt context is totally bad idea, and then
found the following commit.
http://git.kernel.org/cgit/linux/kernel/git/stable/li
4 matches
Mail list logo