On (06/26/18 07:03), Dmitry Vyukov wrote: > > I don't think this is a printk() issue per se, so I think Option B is > > the only option. You should not get stuck in an infinite loop if we run > > short on memory. Perhaps we could have an Option C which would exit > > this loop gracefully with some kind of error. But I haven't looked at > > the surrounding code to be sure if that is possible. > > I suspect this is not even OOM. Could be. But at the same time it stalls RCU, so OOM at some point becomes realistic. -ss
