Re: [PATCH v14 1/2] Reorganize the oom report in dump_header

On Mon 23-07-18 10:56:13, 禹舟键 wrote: > Hi Michal > OK, thanks. Is there any problems for V14? I do not know of any. Both patches are sitting in the mmotm tree so they should be merged in a forseeable future as long as nobody finds any problems. -- Michal Hocko SUSE Labs

Re: [PATCH v14 1/2] Reorganize the oom report in dump_header

Hi Michal OK, thanks. Is there any problems for V14? Thanks

Re: [PATCH v14 1/2] Reorganize the oom report in dump_header

On Tue 17-07-18 19:05:47, ufo19890...@gmail.com wrote: > From: yuzhoujian > > OOM report contains several sections. The first one is the allocation > context that has triggered the OOM. Then we have cpuset context > followed by the stack trace of the OOM path. Followed by the oom > eligible tasks

[PATCH v14 1/2] Reorganize the oom report in dump_header

From: yuzhoujian OOM report contains several sections. The first one is the allocation context that has triggered the OOM. Then we have cpuset context followed by the stack trace of the OOM path. Followed by the oom eligible tasks and the information about the chosen oom victim. One thing that m