From: Ning Qu <quning@gmail.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Matthew Wilcox <willy@linux.intel.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
linux-fsdevel@vger.kernel.org, Hugh Dickins <hughd@google.com>,
Mel Gorman <mgorman@suse.de>, Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Wu Fengguang <fengguang.wu@intel.com>, Jan Kara <jack@suse.cz>,
Dave Hansen <dave@sr71.net>,
linux-mm@kvack.org, Hillf Danton <dhillf@gmail.com>
Subject: Re: [PATCH] thp: Fix deadlock situation in vma_adjust with huge page in page cache
Date: Mon, 12 Aug 2013 09:42:42 -0700 [thread overview]
Message-ID: <CACQD4-5Aie7c=QTVgWkf76fEsWOuR52PZHi0YLfrqdbX5bY03w@mail.gmail.com> (raw)
In-Reply-To: <20130812135509.DDF5FE0090@blue.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
That's great!
Best wishes,
--
Ning Qu
On Mon, Aug 12, 2013 at 6:55 AM, Kirill A. Shutemov <
kirill.shutemov@linux.intel.com> wrote:
> Ning Qu wrote:
> > In vma_adjust, the current code grabs i_mmap_mutex before calling
> > vma_adjust_trans_huge. This used to be fine until huge page in page
> > cache comes in. The problem is the underlying function
> > split_file_huge_page will also grab the i_mmap_mutex before splitting
> > the huge page in page cache. Obviously this is causing deadlock
> > situation.
> >
> > This fix is to move the vma_adjust_trans_huge before grab the lock for
> > file, the same as what the function is currently doing for anonymous
> > memory.
> >
> > Tested, everything works fine so far.
> >
> > Signed-off-by: Ning Qu <quning@google.com>
>
> Thanks, applied.
>
> --
> Kirill A. Shutemov
>
[-- Attachment #2: Type: text/html, Size: 1423 bytes --]
next prev parent reply other threads:[~2013-08-12 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 6:28 Ning Qu
2013-08-12 13:55 ` Kirill A. Shutemov
2013-08-12 16:42 ` Ning Qu [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-09 21:34 Ning Qu
2013-08-10 5:22 ` Ning Qu
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='CACQD4-5Aie7c=QTVgWkf76fEsWOuR52PZHi0YLfrqdbX5bY03w@mail.gmail.com' \
--to=quning@gmail.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave@sr71.net \
--cc=dhillf@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.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