From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: xiaolong.ye@intel.com, lkp@01.org
Cc: kirill@shutemov.name, akpm@linux-foundation.org,
linux-mm@kvack.org, kirill.shutemov@linux.intel.com,
mhocko@suse.com
Subject: Re: [lkp-robot] [mm] 67ffc906f8:WARNING:at_mm/filemap.c:#__warn_lock_page_from_reclaim_context
Date: Thu, 29 Mar 2018 19:32:11 +0900 [thread overview]
Message-ID: <201803291932.AJH35913.JOQSFFtOLFOVHM@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20180329070409.GF4172@yexl-desktop>
kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-4.9):
>
> commit: 67ffc906f8dee0e0433cad83dbdd198e5d1fc86f ("mm: Warn on lock_page() from reclaim context.")
> url: https://github.com/0day-ci/linux/commits/Tetsuo-Handa/mm-Warn-on-lock_page-from-reclaim-context/20180318-173622
Thanks. Already fixed in v4.16-rc7.
commit b3cd54b257ad95d344d121dc563d943ca39b0921
Author: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Date: Thu Mar 22 16:17:35 2018 -0700
mm/shmem: do not wait for lock_page() in shmem_unused_huge_shrink()
> [ 60.850212] CPU: 0 PID: 221 Comm: sed Not tainted 4.16.0-rc4-00340-g67ffc90 #2
prev parent reply other threads:[~2018-03-29 10:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 14:11 [PATCH] mm: Warn on lock_page() from reclaim context Tetsuo Handa
2018-03-17 15:54 ` Kirill A. Shutemov
2018-03-18 1:22 ` [PATCH v2] " Tetsuo Handa
2018-03-18 8:55 ` Kirill A. Shutemov
2018-03-19 9:04 ` Michal Hocko
2018-03-19 10:14 ` Kirill A. Shutemov
2018-03-19 10:33 ` Michal Hocko
2018-03-19 10:45 ` Kirill A. Shutemov
2018-03-19 10:55 ` Michal Hocko
2018-03-19 12:04 ` Tetsuo Handa
2018-03-19 22:08 ` Andrew Morton
2018-03-20 8:44 ` Michal Hocko
2018-03-20 17:50 ` Andrew Morton
2018-03-29 7:04 ` [lkp-robot] [mm] 67ffc906f8: WARNING:at_mm/filemap.c:#__warn_lock_page_from_reclaim_context kernel test robot
2018-03-29 10:32 ` Tetsuo Handa [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=201803291932.AJH35913.JOQSFFtOLFOVHM@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-mm@kvack.org \
--cc=lkp@01.org \
--cc=mhocko@suse.com \
--cc=xiaolong.ye@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