From: Michal Hocko <mhocko@kernel.org>
To: Yang Shi <yang.shi@linux.alibaba.com>
Cc: kirill@shutemov.name, willy@infradead.org,
ldufour@linux.vnet.ibm.com, vbabka@suse.cz,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2 -mm] mm: brk: dwongrade mmap_sem to read when shrinking
Date: Wed, 26 Sep 2018 10:17:08 +0200 [thread overview]
Message-ID: <20180926081708.GG6278@dhcp22.suse.cz> (raw)
In-Reply-To: <1537922816-108051-2-git-send-email-yang.shi@linux.alibaba.com>
On Wed 26-09-18 08:46:56, Yang Shi wrote:
> brk might be used to shinrk memory mapping too. Use __do_munmap() to
> shrink mapping with downgrading mmap_sem to read.
same comment wrt the changelog as for the previous patch.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-09-26 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 0:46 [PATCH 1/2 -mm] mm: mremap: " Yang Shi
2018-09-26 0:46 ` [PATCH 2/2 -mm] mm: brk: " Yang Shi
2018-09-26 8:17 ` Michal Hocko [this message]
2018-09-26 8:16 ` [PATCH 1/2 -mm] mm: mremap: " Michal Hocko
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=20180926081708.GG6278@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kirill@shutemov.name \
--cc=ldufour@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yang.shi@linux.alibaba.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