From: Li Zhijian <zhijianx.li@intel.com>
To: Li Zhijian <lizhijian@cn.fujitsu.com>, Dan Rue <dan.rue@linaro.org>
Cc: linux-kselftest@vger.kernel.org, "Li,
Philip" <philip.li@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [kselftests] compaction_test is blocked
Date: Mon, 12 Feb 2018 11:26:39 +0800 [thread overview]
Message-ID: <30e882ea-1e79-44bf-9a85-c0be105ec218@intel.com> (raw)
In-Reply-To: <7c95e7cc-1955-ba99-9aa5-4bf5d994bd58@cn.fujitsu.com>
On 2018年02月11日 13:44, Li Zhijian wrote:
>
>
> On 02/10/2018 05:11 AM, Dan Rue wrote:
>> On Fri, Feb 09, 2018 at 03:53:59PM +0800, Li Zhijian wrote:
>>> Hi
>>>
>>> kselftests is integrated Intel 0Day project.
>>> Sometimes we found compaction_test is blocked for more than 1 hours
>>> until i kill it.
>>>
>>> Try to figure out where it is running, i added some log to this case.
>>>
>>> the test log is like:
>>> -------------------
>>> [ 111.750543] main: 248
>>> [ 111.750544]-
>>> [ 111.750821] check_compaction: 98
>>> [ 111.750822]-
>>> [ 111.751102] check_compaction: 105
>>> [ 111.751103]-
>>> [ 111.751362] check_compaction: 111
>>> [ 111.751363]-
>>> [ 111.751621] check_compaction: 118
>>> [ 111.751622]-
>>> [ 111.751879] check_compaction: 123
>>> [ 111.751880]-
>>> -------------------
>>> 118 fprintf(stderr, "%s: %d\n", __func__, __LINE__);
>>> 119 lseek(fd, 0, SEEK_SET);
>>> 120
>>> 121 /* Request a large number of huge pages. The Kernel will
>>> allocate
>>> 122 as much as it can */
>>> 123 fprintf(stderr, "%s: %d\n", __func__, __LINE__);
>>> <<<======== the last line we can catch.
>>> 124 if (write(fd, "100000", (6*sizeof(char))) !=
>>> (6*sizeof(char))) { <<<<============ blocking position
>>> 125 perror("Failed to write 100000 to
>>> /proc/sys/vm/nr_hugepages\n");
>>> 126 goto close_fd;
>>> 127 }
>>> 128
>>> 129 lseek(fd, 0, SEEK_SET);
>>> 130
>>> 131 fprintf(stderr, "%s: %d\n", __func__, __LINE__);
>>> 132 if (read(fd, nr_hugepages, sizeof(nr_hugepages)) <= 0) {
>>> 133 perror("Failed to re-read from
>>> /proc/sys/vm/nr_hugepages\n");
>>> 134 goto close_fd;
>>> 135 }
>>> -------------------
>>>
>>> According to above log and code, it most likely it is blocking at
>>> the writing operation.
>>>
>>> my environment is like:
>>> OS: debian
>>> kernel: v4.15
>>> model: Ivytown Ivy Bridge-EP
>>> nr_cpu: 48
>>> memory: 64G
>> Hi Zhijian,
>>
>> Please try this patch in mainline:
>>
>> 4c1baad22390 kselftest: fix OOM in memory compaction test
>
> Hi Dan
>
> Thanks for your replies.
>
> I run this case on v4.15, looks this patch is already merged to v4.15.
> lizhijian@inn:~/linux$ git describe 4c1baad
> v4.15-rc2-2-g4c1baad223906
My mistake, this path is not contained by v4.15 yet.
i will have a try.
Thanks
>
> Thanks
>
>> Dan
>>
>>>
>>> NOTE: 0Day can reproduce this issue in 20% on 0Day.
>>>
>>> Anybody can help have a look?
>>>
>>> Thanks
>>> Zhjian
>>>
>>>
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe
>>> linux-kselftest" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>> .
>>
>
next prev parent reply other threads:[~2018-02-12 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 7:53 Li Zhijian
2018-02-09 21:11 ` Dan Rue
2018-02-11 5:44 ` Li Zhijian
2018-02-12 3:26 ` Li Zhijian [this message]
2018-02-12 9:58 ` Li Zhijian
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=30e882ea-1e79-44bf-9a85-c0be105ec218@intel.com \
--to=zhijianx.li@intel.com \
--cc=dan.rue@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizhijian@cn.fujitsu.com \
--cc=philip.li@intel.com \
/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®