From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
paulus@samba.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH V2] powerpc: thp: Fix crash on mremap
Date: Sat, 15 Feb 2014 08:34:19 +1100 [thread overview]
Message-ID: <1392413659.10050.14.camel@pasglop> (raw)
In-Reply-To: <1392239014.3835.148.camel@pasglop>
On Thu, 2014-02-13 at 08:03 +1100, Benjamin Herrenschmidt wrote:
> It looks very different because the function that needs to be fixed
> changed a lot upstream in 3.13.
.../...
Hi Greg !
You didn't say if that explanation was to your liking :-)
If it is, do you want Aneesh to re-submit the patch with such an
explanation in the changelog ?
Cheers,
Ben.
> In practice it's *not* very different in behaviour. It's just that
> on powerpc we need to unconditionally call withdraw and deposit when
> moving PTEs or it will crash, due to how we keep the transparent
> huge page in sync with the hash table.
>
> With the 3.13 code, due to lock breaking introduced by Kirill in
> 3.13-rc's, there's already a generic case for doing that (if we dropped
> the lock). So we just changed the condition to essentially force the
> condition to true to always do it under control of an arch helper.
>
> The pre-3.13 code didn't do the withdraw and deposit at all in that
> function however, so in that case, the patch (this 3.12 one) basically
> just adds the calls to withdraw and deposit under control of an ifdef
> which is only enabled for powerpc64.
>
> So you are taking 0 risk with other architecture and as the powerpc
> maintainer I'm happy with the patch.
>
> Cheers,
> Ben.
>
>
prev parent reply other threads:[~2014-02-14 21:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 13:51 [PATCH V2] powerpc: thp: Fix crash on mremap Aneesh Kumar K.V
2014-02-11 17:31 ` Greg KH
2014-02-11 18:52 ` Benjamin Herrenschmidt
2014-02-12 2:54 ` Aneesh Kumar K.V
2014-02-12 2:52 ` Aneesh Kumar K.V
2014-02-12 14:23 ` Greg KH
2014-02-12 15:11 ` Aneesh Kumar K.V
2014-02-12 21:03 ` Benjamin Herrenschmidt
2014-02-14 21:34 ` Benjamin Herrenschmidt [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=1392413659.10050.14.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.