From: Rong Chen <rong.a.chen@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [LKP] [mm/memory.c] 6558038e45: general_protection_fault:#[##]
Date: Fri, 19 Oct 2018 15:12:54 +0800 [thread overview]
Message-ID: <35a54261-965e-dc03-ef8e-3a44faa8846e@intel.com> (raw)
In-Reply-To: <20181017152621.7e716f4906f81c52c67d59c3@linux-foundation.org>
On 10/18/2018 06:26 AM, Andrew Morton wrote:
> On Wed, 17 Oct 2018 09:36:00 +0800 kernel test robot <rong.a.chen@intel.com> wrote:
>
>> FYI, we noticed the following commit (built with gcc-6):
>>
>> commit: 6558038e4540a22ee4f99a5def74791189102bc0 ("mm/memory.c: recheck page table entry with page table lock held")
>> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
>>
>> in testcase: trinity
>> with following parameters:
>>
>> runtime: 300s
>>
>> test-description: Trinity is a linux system call fuzz tester.
>> test-url: http://codemonkey.org.uk/projects/trinity/
>>
>>
>> on test machine: qemu-system-x86_64 -enable-kvm -cpu qemu64,+ssse3 -smp 4 -m 4G
>>
>> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> mm-recheck-page-table-entry-with-page-table-lock-held-fix.patch ("mm:
> fix the crash observed with syzkaller run") will most likely fix this.
> Was it applied during this testing?
It wasn't applied during this testing.
Best Regards,
Rong Chen
prev parent reply other threads:[~2018-10-19 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 1:36 kernel test robot
2018-10-17 22:26 ` Andrew Morton
2018-10-19 7:12 ` Rong Chen [this message]
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=35a54261-965e-dc03-ef8e-3a44faa8846e@intel.com \
--to=rong.a.chen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®