linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Michal Hocko <mhocko@kernel.org>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org,
	Eric Wheeler <linux-mm@lists.ewheeler.net>,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Subject: Re: [PATCH] mm/shmem: Do not wait for lock_page() in shmem_unused_huge_shrink()
Date: Fri, 16 Mar 2018 16:02:00 +0300	[thread overview]
Message-ID: <20180316130200.rbke66zjyoc6zwzl@node.shutemov.name> (raw)
In-Reply-To: <20180316125827.GC11461@dhcp22.suse.cz>

On Fri, Mar 16, 2018 at 01:58:27PM +0100, Michal Hocko wrote:
> On Fri 16-03-18 15:25:08, Kirill A. Shutemov wrote:
> > On Fri, Mar 16, 2018 at 01:13:03PM +0100, Michal Hocko wrote:
> > > On Fri 16-03-18 13:59:08, Kirill A. Shutemov wrote:
> > > [..]
> > > > @@ -498,31 +498,42 @@ static unsigned long shmem_unused_huge_shrink(struct shmem_sb_info *sbinfo,
> > > >  			continue;
> > > >  		}
> > > >  
> > > > -		page = find_lock_page(inode->i_mapping,
> > > > +		page = find_get_page(inode->i_mapping,
> > > >  				(inode->i_size & HPAGE_PMD_MASK) >> PAGE_SHIFT);
> > > >  		if (!page)
> > > >  			goto drop;
> > > >  
> > > > +		/* No huge page at the end of the file: nothing to split */
> > > >  		if (!PageTransHuge(page)) {
> > > > -			unlock_page(page);
> > > >  			put_page(page);
> > > >  			goto drop;
> > > >  		}
> > > >  
> > > > +		/*
> > > > +		 * Leave the inode on the list if we failed to lock
> > > > +		 * the page at this time.
> > > > +		 *
> > > > +		 * Waiting for the lock may lead to deadlock in the
> > > > +		 * reclaim path.
> > > > +		 */
> > > > +		if (!trylock_page(page)) {
> > > > +			put_page(page);
> > > > +			goto leave;
> > > > +		}
> > > 
> > > Can somebody split the huge page after the PageTransHuge check and
> > > before we lock it?
> > 
> > Nope. Pin on the page is enough to prevent split.
> 
> Good, I thought so but wasn't really 100% sure. Thanks for the
> clarification and feel free to add
> Acked-by: Michal Hocko <mhocko@suse.com>

Thanks.

> Maybe you should stick
> Reported-by: Eric Wheeler <linux-mm@lists.ewheeler.net>
> and point to http://lkml.kernel.org/r/alpine.LRH.2.11.1801242349220.30642@mail.ewheeler.net
> because that smells like a bug that this patch would be fixing.

Good point.

Andrew, do you want me repost with tags integrated?

-- 
 Kirill A. Shutemov

  reply	other threads:[~2018-03-16 13:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 10:59 Kirill A. Shutemov
2018-03-16 12:13 ` Michal Hocko
2018-03-16 12:25   ` Kirill A. Shutemov
2018-03-16 12:58     ` Michal Hocko
2018-03-16 13:02       ` Kirill A. Shutemov [this message]
2018-03-16 13:14         ` Tetsuo Handa
2018-03-16 13:20           ` Michal Hocko
2018-03-16 13:34           ` Kirill A. Shutemov
2018-03-16 14:42             ` Tetsuo Handa

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=20180316130200.rbke66zjyoc6zwzl@node.shutemov.name \
    --to=kirill@shutemov.name \
    --cc=akpm@linux-foundation.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-mm@lists.ewheeler.net \
    --cc=mhocko@kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=stable@vger.kernel.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