From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
linux-mm@kvack.org, xen-devel@lists.xenproject.org,
LKML <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@suse.com>, Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH] xen/gntdev: fix up blockable calls to mn_invl_range_start
Date: Thu, 23 Aug 2018 09:46:40 -0400 [thread overview]
Message-ID: <565d0ef0-4723-bd1b-95de-cb9aba50fe20@oracle.com> (raw)
In-Reply-To: <20180823120707.10998-1-mhocko@kernel.org>
On 08/23/2018 08:07 AM, Michal Hocko wrote:
> From: Michal Hocko <mhocko@suse.com>
>
> 93065ac753e4 ("mm, oom: distinguish blockable mode for mmu notifiers")
> has introduced blockable parameter to all mmu_notifiers and the notifier
> has to back off when called in !blockable case and it could block down
> the road.
>
> The above commit implemented that for mn_invl_range_start but both
> in_range checks are done unconditionally regardless of the blockable
> mode and as such they would fail all the time for regular calls.
> Fix this by checking blockable parameter as well.
>
> Once we are there we can remove the stale TODO. The lock has to be
> sleepable because we wait for completion down in gnttab_unmap_refs_sync.
>
> Fixes: 93065ac753e4 ("mm, oom: distinguish blockable mode for mmu notifiers")
> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> Cc: Juergen Gross <jgross@suse.com>
> Signed-off-by: Michal Hocko <mhocko@suse.com>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracel.com>
prev parent reply other threads:[~2018-08-23 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 12:07 Michal Hocko
2018-08-23 13:44 ` Tetsuo Handa
2018-08-23 13:51 ` Michal Hocko
2018-08-23 14:06 ` Boris Ostrovsky
2018-08-23 19:09 ` Michal Hocko
2018-08-24 5:03 ` Juergen Gross
2018-08-24 7:49 ` Michal Hocko
2018-08-23 14:20 ` Tetsuo Handa
2018-08-23 13:46 ` Boris Ostrovsky [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=565d0ef0-4723-bd1b-95de-cb9aba50fe20@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=xen-devel@lists.xenproject.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 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®