All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: lkp@01.org, 0day robot <lkp@intel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [mm, oom] 6209f6fc62: general_protection_fault:#[##]
Date: Tue, 25 Sep 2018 15:43:22 +0800	[thread overview]
Message-ID: <917270d5-8755-b0d6-60c4-871f8c7ff982@intel.com> (raw)
In-Reply-To: <20180925073145.GO18685@dhcp22.suse.cz>



On 09/25/2018 03:31 PM, Michal Hocko wrote:
> On Tue 25-09-18 15:00:15, Rong Chen wrote:
>>
>> On 09/25/2018 02:06 PM, Michal Hocko wrote:
>>> On Tue 25-09-18 13:48:20, kernel test robot wrote:
>>>> FYI, we noticed the following commit (built with gcc-7):
>>>>
>>>> commit: 6209f6fc62835d84c2a92d237588a114e39436ce ("mm, oom: rework mmap_exit vs. oom_reaper synchronization")
>>>> https://github.com/0day-ci/linux UPDATE-20180911-024633/Tetsuo-Handa/mm-oom-Fix-unnecessary-killing-of-additional-processes/20180910-163452
>>> Do you have a msg-id to the patch that has been tested?
>> message_id: 20180910125513.311-2-mhocko@kernel.org
> Thanks! It woudl be really great if this was a part of the report when
> testing patches which are not mainline yet.
>
> This patch resulting in a crash is quite surprising. The patch is RFC
> and not tested yet but I will definitely have a look. Could you help me
> some more and give faddr2line __oom_reap_task_mm+0x40 please?
$ faddr2line ./vmlinux __oom_reap_task_mm+0x40
__oom_reap_task_mm+0x40/0x175:
can_madv_dontneed_vma at mm/internal.h:48
  (inlined by) __oom_reap_task_mm at mm/oom_kill.c:505

Best Regards,
Rong Chen

WARNING: multiple messages have this Message-ID (diff)
From: Rong Chen <rong.a.chen@intel.com>
To: lkp@lists.01.org
Subject: Re: [mm, oom] 6209f6fc62: general_protection_fault:#[##]
Date: Tue, 25 Sep 2018 15:43:22 +0800	[thread overview]
Message-ID: <917270d5-8755-b0d6-60c4-871f8c7ff982@intel.com> (raw)
In-Reply-To: <20180925073145.GO18685@dhcp22.suse.cz>

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]



On 09/25/2018 03:31 PM, Michal Hocko wrote:
> On Tue 25-09-18 15:00:15, Rong Chen wrote:
>>
>> On 09/25/2018 02:06 PM, Michal Hocko wrote:
>>> On Tue 25-09-18 13:48:20, kernel test robot wrote:
>>>> FYI, we noticed the following commit (built with gcc-7):
>>>>
>>>> commit: 6209f6fc62835d84c2a92d237588a114e39436ce ("mm, oom: rework mmap_exit vs. oom_reaper synchronization")
>>>> https://github.com/0day-ci/linux UPDATE-20180911-024633/Tetsuo-Handa/mm-oom-Fix-unnecessary-killing-of-additional-processes/20180910-163452
>>> Do you have a msg-id to the patch that has been tested?
>> message_id: 20180910125513.311-2-mhocko(a)kernel.org
> Thanks! It woudl be really great if this was a part of the report when
> testing patches which are not mainline yet.
>
> This patch resulting in a crash is quite surprising. The patch is RFC
> and not tested yet but I will definitely have a look. Could you help me
> some more and give faddr2line __oom_reap_task_mm+0x40 please?
$ faddr2line ./vmlinux __oom_reap_task_mm+0x40
__oom_reap_task_mm+0x40/0x175:
can_madv_dontneed_vma at mm/internal.h:48
  (inlined by) __oom_reap_task_mm at mm/oom_kill.c:505

Best Regards,
Rong Chen

  reply	other threads:[~2018-09-25  7:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25  5:48 [LKP] [mm, oom] 6209f6fc62: general_protection_fault:#[##] kernel test robot
2018-09-25  5:48 ` kernel test robot
2018-09-25  6:06 ` [LKP] " Michal Hocko
2018-09-25  6:06   ` Michal Hocko
2018-09-25  7:00   ` [LKP] " Rong Chen
2018-09-25  7:00     ` Rong Chen
2018-09-25  7:31     ` [LKP] " Michal Hocko
2018-09-25  7:31       ` Michal Hocko
2018-09-25  7:43       ` Rong Chen [this message]
2018-09-25  7:43         ` Rong Chen
2018-09-25  7:59         ` [LKP] " Michal Hocko
2018-09-25  7:59           ` Michal Hocko
2018-09-25  8:09           ` Rong Chen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=917270d5-8755-b0d6-60c4-871f8c7ff982@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=lkp@intel.com \
    --cc=mhocko@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.