On 2018/12/31 17:24, Dmitry Vyukov wrote: >>> Since this involves OOMs and looks like a one-off induced memory corruption: >>> >>> #syz dup: kernel panic: corrupted stack end in wb_workfn >>> >> >> Why? >> >> RCU stall in this case is likely to be latency caused by flooding of printk(). > > Just a hypothesis. OOMs lead to arbitrary memory corruptions, so can > cause stalls as well. But can be what you said too. I just thought > that cleaner dashboard is more useful than a large assorted pile of > crashes. If you think it's actionable in some way, feel free to undup. > We don't know why bpf tree is hitting this problem. Let's continue monitoring this problem. #syz undup
