Messages in this thread | | | Subject | Re: [PATCH] oom: always panic on OOM when panic_on_oom is configured | From | Tetsuo Handa <> | Date | Mon, 8 Jun 2015 20:53:18 +0900 |
| |
Michal Hocko wrote: > On Sat 06-06-15 15:51:35, Tetsuo Handa wrote: > > For me, !__GFP_FS allocations not calling out_of_memory() _forever_ is a > > violation of the user policy. > > Yes, the current behavior of GFP_NOFS is highly suboptimal, but this has > _nothing_ what so ever to do with this patch and panic_on_oom handling. > The former one is the page allocator proper while we are in the OOM > killer layer here. > > This is not the first time you have done that. Please stop it. It makes > a complete mess of the original discussions.
My specific area of expertise in Linux kernel is security/tomoyo/ directory. What I could contribute with other areas is to pay attention to potential possibilities. But I'm such outsider about other areas that I can't differentiate the page allocator proper from the OOM killer layer.
Excuse me for focusing on the wrong issue, but I will likely unconsciously make the same mistake again. Please ignore or point out when I made mistakes.
| |