It's interesting that this was known for 3+ years, but nobody bothered adding a small warning to the code. We noticed this because it's actually happening on Chromebooks in the field. We try to minimize OOM kills, but we can deal with them. Of course, a hung kernel we cannot deal with. On Tue, Nov 5, 2013 at 7:04 PM, Sameer Nanda <snanda@xxxxxxxxxxxx> wrote: > > > > On Tue, Nov 5, 2013 at 5:27 PM, David Rientjes <rientjes@xxxxxxxxxx> wrote: >> >> On Tue, 5 Nov 2013, Luigi Semenzato wrote: >> >> > It's not enough to hold a reference to the task struct, because it can >> > still be taken out of the circular list of threads. The RCU >> > assumptions don't hold in that case. >> > >> >> Could you please post a proper bug report that isolates this at the cause? > > > We've been running into this issue on Chrome OS. crbug.com/256326 has > additional > details. The issue manifests itself as a soft lockup. > > The kernel we've been seeing this on is 3.8. > > We have a pretty consistent repro currently. Happy to try out other > suggestions > for a fix. > >> >> >> Thanks. > > > > > -- > Sameer -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>