On Wed 21-11-18 19:29:58, 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. The tird one is the OOM
> memory
On Wed 21-11-18 19:29:58, 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. The tird one is the OOM
> memory
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. The tird one is the OOM
memory information. Followed by the current memory state of all system
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. The tird one is the OOM
memory information. Followed by the current memory state of all system
On Fri 02-11-18 14:18:59, 禹舟键 wrote:
> Hi Michal
> The message-id is as below
> https://lkml.org/lkml/2018/7/31/148
David said
: It's possible that p is NULL when calling dump_header(). In this case we
: do not want to print any line concerning a victim because no oom kill has
: occurred.
This
On Fri 02-11-18 14:18:59, 禹舟键 wrote:
> Hi Michal
> The message-id is as below
> https://lkml.org/lkml/2018/7/31/148
David said
: It's possible that p is NULL when calling dump_header(). In this case we
: do not want to print any line concerning a victim because no oom kill has
: occurred.
This
On Thu 01-11-18 18:09:39, 禹舟键 wrote:
> Hi Michal
> The null pointer is possible when calling the dump_header, this bug was
> detected by LKP. Below is the context 3 months ago.
Yeah I remember it was 0day report but I coundn't find it in my email
archive. Do you happen to have a message-id?
On Thu 01-11-18 18:09:39, 禹舟键 wrote:
> Hi Michal
> The null pointer is possible when calling the dump_header, this bug was
> detected by LKP. Below is the context 3 months ago.
Yeah I remember it was 0day report but I coundn't find it in my email
archive. Do you happen to have a message-id?
On Sat 29-09-18 21:06:26, ufo19890...@gmail.com wrote:
[...]
> Changes since v14:
> - add the dump_oom_summary for the single line output of oom context.
> - fix the null pointer in the dump_header.
I do not remember details about this null ptr but the fix you seemed to
have done is
[...]
>
On Sat 29-09-18 21:06:26, ufo19890...@gmail.com wrote:
[...]
> Changes since v14:
> - add the dump_oom_summary for the single line output of oom context.
> - fix the null pointer in the dump_header.
I do not remember details about this null ptr but the fix you seemed to
have done is
[...]
>
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. The tird one is the OOM
memory information. Followed by the current memory state of all system
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. The tird one is the OOM
memory information. Followed by the current memory state of all system
12 matches
Mail list logo
