linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Bob Liu <lliubbo@gmail.com>, Sasha Levin <sasha.levin@oracle.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: mm: NULL ptr deref in balance_dirty_pages_ratelimited
Date: Wed, 26 Feb 2014 07:45:34 -0800	[thread overview]
Message-ID: <20140226154534.GJ8264@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140226152051.GA31115@node.dhcp.inet.fi>

On Wed, Feb 26, 2014 at 05:20:51PM +0200, Kirill A. Shutemov wrote:
> On Wed, Feb 26, 2014 at 10:48:30PM +0800, Bob Liu wrote:
> > > Do you relay on unlock_page() to have a compiler barrier?
> > >
> > 
> > Before your commit mapping is a local variable and be assigned before
> > unlock_page():
> > struct address_space *mapping = page->mapping;
> > unlock_page(dirty_page);
> > put_page(dirty_page);
> > if ((dirtied || page_mkwrite) && mapping) {
> > 
> > 
> > I'm afraid now "fault_page->mapping" might be changed to NULL after
> > "if ((dirtied || vma->vm_ops->page_mkwrite) && fault_page->mapping) {"
> > and then passed down to balance_dirty_pages_ratelimited(NULL).
> 
> I see what you try to fix. I wounder if we need to do
> 
> mapping = ACCESS_ONCE(fault_page->mapping);
> 
> instead.
> 
> The question is if compiler on its own can eliminate intermediate variable
> and dereference fault_page->mapping twice, as code with my patch does.
> I ask because smp_mb__after_clear_bit() in unlock_page() does nothing on
> some architectures.

The compiler is most definitely within its rights to eliminate intermediate
variables if you don't use something like ACCESS_ONCE().  For more info,
see the LWN writeup:  http://lwn.net/Articles/508991/

							Thanx, Paul

> > >>
> > >> diff --git a/mm/memory.c b/mm/memory.c
> > >> index 548d97e..90cea22 100644
> > >> --- a/mm/memory.c
> > >> +++ b/mm/memory.c
> > >> @@ -3419,6 +3419,7 @@ static int do_shared_fault(struct mm_struct *mm,
> > >> struct vm_area_struct *vma,
> > >>   pgoff_t pgoff, unsigned int flags, pte_t orig_pte)
> > >>  {
> > >>   struct page *fault_page;
> > >> + struct address_space *mapping;
> > >>   spinlock_t *ptl;
> > >>   pte_t *pte;
> > >>   int dirtied = 0;
> > >> @@ -3454,13 +3455,14 @@ static int do_shared_fault(struct mm_struct
> > >> *mm, struct vm_area_struct *vma,
> > >>
> > >>   if (set_page_dirty(fault_page))
> > >>   dirtied = 1;
> > >> + mapping = fault_page->mapping;
> > >>   unlock_page(fault_page);
> > >> - if ((dirtied || vma->vm_ops->page_mkwrite) && fault_page->mapping) {
> > >> + if ((dirtied || vma->vm_ops->page_mkwrite) && mapping) {
> > >>   /*
> > >>   * Some device drivers do not set page.mapping but still
> > >>   * dirty their pages
> > >>   */
> > >> - balance_dirty_pages_ratelimited(fault_page->mapping);
> > >> + balance_dirty_pages_ratelimited(mapping);
> > >>   }
> > >>
> > >>   /* file_update_time outside page_lock */
> > >> --
> > >> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > >> the body of a message to majordomo@vger.kernel.org
> > >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > >> Please read the FAQ at  http://www.tux.org/lkml/
> > >
> > > --
> > >  Kirill A. Shutemov
> > 
> > -- 
> > Regards,
> > --Bob
> 
> -- 
>  Kirill A. Shutemov
> 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2014-02-26 15:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 19:32 mm: NULL ptr deref in balance_dirty_pages_ratelimited Sasha Levin
2014-02-26  7:15 ` Bob Liu
2014-02-26 14:09   ` Kirill A. Shutemov
2014-02-26 14:48     ` Bob Liu
2014-02-26 15:20       ` Kirill A. Shutemov
2014-02-26 15:45         ` Paul E. McKenney [this message]
2014-02-26 15:47         ` Peter Zijlstra

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=20140226154534.GJ8264@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lliubbo@gmail.com \
    --cc=peterz@infradead.org \
    --cc=sasha.levin@oracle.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;
as well as URLs for NNTP newsgroup(s).