On Tue, 11 Oct 2011, Tejun Heo wrote: > > If that's possible, then we can just add Tejun to add a follow-up patch to > > remove the thaw directly in the oom killer. I'm thinking that won't be > > possible for 3.2, though, so I don't know why we'd remove > > oom-thaw-threads-if-oom-killed-thread-is-frozen-before-deferring.patch > > from -mm? > > Yeah, it's a bit unclear. All (or at least most) patches which were > necessary for this patch was queued in Rafael's tree before korg went > belly up and then we both lost track of the tree and I need to > regenerate the tree and ask Rafael to pull again. Eek, what a pain. > I think the merge > window is already too close, so please go ahead with the acked fix. > Let's clean it up during the next devel cycle. > Ok, sounds good. When frozen oom killed threads can always move down the exit path, then we can just remember to remove the thaw_process() from the oom killer. Thanks. -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>