linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Weiny, Ira" <ira.weiny@intel.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Vlastimil Babka <vbabka@suse.cz>, Michal Hocko <mhocko@suse.com>,
	Matthew Wilcox <willy@infradead.org>,
	Linux MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH RFC] mm/swap: make release_pages() and put_pages() match
Date: Fri, 24 May 2019 20:08:42 +0000	[thread overview]
Message-ID: <2807E5FD2F6FDA4886F6618EAC48510E79D3ACC3@CRSMSX101.amr.corp.intel.com> (raw)
In-Reply-To: <CALvZod6skK6NxeRXjKS64+1jpF9NwbLp7DhpWueB0F6Tj4MNUw@mail.gmail.com>

> 
> On Fri, May 24, 2019 at 12:33 PM <ira.weiny@intel.com> wrote:
> >
> > From: Ira Weiny <ira.weiny@intel.com>
> >
> > RFC I have no idea if this is correct or not.  But looking at
> > release_pages() I see a call to both __ClearPageActive() and
> > __ClearPageWaiters() while in __page_cache_release() I do not.
> >
> > Is this a bug which needs to be fixed?  Did I miss clearing active
> > somewhere else in the call chain of put_page?
> >
> > This was found via code inspection while determining if
> > release_pages() and the new put_user_pages() could be interchangeable.
> >
> > Signed-off-by: Ira Weiny <ira.weiny@intel.com>
> > ---
> >  mm/swap.c | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/mm/swap.c b/mm/swap.c
> > index 3a75722e68a9..9d0432baddb0 100644
> > --- a/mm/swap.c
> > +++ b/mm/swap.c
> > @@ -69,6 +69,7 @@ static void __page_cache_release(struct page *page)
> >                 del_page_from_lru_list(page, lruvec,
> > page_off_lru(page));
> 
> see page_off_lru(page) above which clear active bit.

Thanks,  Sorry for the noise,
Ira


> 
> >                 spin_unlock_irqrestore(&pgdat->lru_lock, flags);
> >         }
> > +       __ClearPageActive(page);
> >         __ClearPageWaiters(page);
> >         mem_cgroup_uncharge(page);
> >  }
> > --
> > 2.20.1
> >

      reply	other threads:[~2019-05-24 20:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-24 19:34 ira.weiny
2019-05-24 19:44 ` Shakeel Butt
2019-05-24 20:08   ` Weiny, Ira [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=2807E5FD2F6FDA4886F6618EAC48510E79D3ACC3@CRSMSX101.amr.corp.intel.com \
    --to=ira.weiny@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=shakeelb@google.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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