mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"axboe@fb.com" <axboe@fb.com>,
	"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
	"kirill.shutemov@linux.intel.com"
	<kirill.shutemov@linux.intel.com>,
	"Huang, Ying" <ying.huang@intel.com>,
	"npiggin@gmail.com" <npiggin@gmail.com>,
	"mingo@kernel.org" <mingo@kernel.org>
Subject: Re: [PATCH] mm: allow page_cache_get_speculative in interrupt context
Date: Tue, 1 Aug 2017 23:51:57 +0300	[thread overview]
Message-ID: <20170801205157.xaec4fcfekxmgxsl@node.shutemov.name> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F0775372496B@SHSMSX103.ccr.corp.intel.com>

On Tue, Aug 01, 2017 at 08:31:14PM +0000, Liang, Kan wrote:
> > 
> > On Tue,  1 Aug 2017 13:39:06 -0400 kan.liang@intel.com wrote:
> > 
> > > Kernel panic when calling the IRQ-safe __get_user_pages_fast in NMI
> > > handler.
> > >
> > > The bug was introduced by commit:
> > >
> > >   2947ba054a4d ("x86/mm/gup: Switch GUP to the generic
> > > get_user_page_fast() implementation")
> > >
> > > The original x86 __get_user_page_fast used plain get_page() or
> > > page_ref_add(). However, the generic __get_user_page_fast uses
> > > page_cache_get_speculative(), which has VM_BUG_ON(in_interrupt()).
> > >
> > > There is no reason to prevent page_cache_get_speculative from using in
> > > interrupt context. According to the author, putting a BUG_ON there is
> > > just because the code is not verifying correctness of interrupt races.
> > > I did some tests in interrupt context. There is no issue found.
> > > Removing VM_BUG_ON(in_interrupt()) for page_cache_get_speculative().
> > 
> > What code calls page_cache_get_speculative() from NMI context?
> >
> 
> The code I'm implementing will call __get_user_page_fast from NMI context.
> __get_user_page_fast will eventually call page_cache_get_speculative().
>  
> > I'm trying to work out which kernel versions need this fix, but there isn't
> > enough info in the changelog for this.  Please don't do that.
> 
> Sorry for the confusion.
> 
> According to the comments, __get_user_page_fast should be IRQ-safe. But it's not.
> This patch could be used to resolve the inconsistencies between the comments
> and implementations for now.
> The generic __get_user_page_fast was introduced by the commit
> 2667f50e8b81457fcb4a3dbe6aff3e81ea009e13
> mm: introduce a general RCU get_user_pages_fast()
> I think the kernel after the commit should be fixed.

I don't think so.

It's 2+ year in and nobody stepped onto this until you with your patchset.
There is no real reason to get it backported.

-- 
 Kirill A. Shutemov

      reply	other threads:[~2017-08-01 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 17:39 kan.liang
2017-08-01 19:49 ` Andrew Morton
2017-08-01 20:31   ` Liang, Kan
2017-08-01 20:51     ` Kirill A. Shutemov [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=20170801205157.xaec4fcfekxmgxsl@node.shutemov.name \
    --to=kirill@shutemov.name \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@fb.com \
    --cc=kan.liang@intel.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=npiggin@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=ying.huang@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

all inboxes | Powered by JetHome®