On Wed 18-02-15 23:06:17, Tetsuo Handa wrote: > Michal Hocko wrote: > > Tetsuo Handa wrote: > > > Michal Hocko wrote: > > > > Because they cannot perform any IO/FS transactions and that would lead > > > > to a premature OOM conditions way too easily. OOM killer is a _last > > > > resort_ reclaim opportunity not something that would happen just because > > > > you happen to be not able to flush dirty pages. > > > > > > But you should not have applied such change without making necessary > > > changes to GFP_NOFS / GFP_NOIO users with such expectation and testing > > > at linux-next.git . Applying such change after 3.19-rc6 is a sucker punch. > > > > This is a nonsense. OOM was disbaled for !__GFP_FS for ages (since > > before git era). > > > Then, at least I expect that filesystem error actions will not be taken so > trivially. Can we apply http://marc.info/?l=linux-mm&m=142418465615672&w=2 for > Linux 3.19-stable? I do not understand. What kind of bug would be fixed by that change? -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
