From: Peter Zijlstra <peterz@infradead.org>
To: Hugh Dickins <hughd@google.com>
Cc: Dave Jones <davej@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: sleeping function warning from __put_anon_vma
Date: Sun, 1 Jun 2014 21:32:40 +0200 [thread overview]
Message-ID: <20140601193240.GF16155@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.LSU.2.11.1405311321340.10272@eggly.anvils>
On Sat, May 31, 2014 at 01:33:13PM -0700, Hugh Dickins wrote:
> [PATCH] mm: fix sleeping function warning from __put_anon_vma
>
> Trinity reports BUG:
> sleeping function called from invalid context at kernel/locking/rwsem.c:47
> in_atomic(): 0, irqs_disabled(): 0, pid: 5787, name: trinity-c27
> __might_sleep < down_write < __put_anon_vma < page_get_anon_vma <
> migrate_pages < compact_zone < compact_zone_order < try_to_compact_pages ..
>
> Right, since conversion to mutex then rwsem, we should not put_anon_vma()
> from inside an rcu_read_lock()ed section: fix the two places that did so.
>
> Fixes: 88c22088bf23 ("mm: optimize page_lock_anon_vma() fast-path")
> Reported-by: Dave Jones <davej@redhat.com>
> Signed-off-by: Hugh Dickins <hughd@google.com>
> Needs-Ack-from: Peter Zijlstra <peterz@infradead.org>
> ---
>
> mm/rmap.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> --- 3.15-rc7/mm/rmap.c 2014-04-13 17:24:36.680507189 -0700
> +++ linux/mm/rmap.c 2014-05-31 12:02:08.496088637 -0700
> @@ -426,12 +426,14 @@ struct anon_vma *page_get_anon_vma(struc
> * above cannot corrupt).
> */
> if (!page_mapped(page)) {
> + rcu_read_unlock();
> put_anon_vma(anon_vma);
> anon_vma = NULL;
> + goto outer;
> }
> out:
> rcu_read_unlock();
> -
> +outer:
> return anon_vma;
> }
I think we can do that without the goto if we write something like:
if (!page_mapped(page)) {
rcu_read_unlock();
put_anon_vma(anon_vma);
return NULL;
}
> @@ -477,9 +479,10 @@ struct anon_vma *page_lock_anon_vma_read
> }
>
> if (!page_mapped(page)) {
> + rcu_read_unlock();
> put_anon_vma(anon_vma);
> anon_vma = NULL;
> - goto out;
> + goto outer;
> }
>
> /* we pinned the anon_vma, its safe to sleep */
> @@ -501,6 +504,7 @@ struct anon_vma *page_lock_anon_vma_read
>
> out:
> rcu_read_unlock();
> +outer:
> return anon_vma;
> }
Same here too, I suppose.
Interesting that we never managed to hit this one; it might also make
sense to put a might_sleep() in anon_vma_free().
Other than that, I don't see anything really odd, then again, its sunday
evening and my thinking cap isn't exactly on proper.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Hugh Dickins <hughd@google.com>
Cc: Dave Jones <davej@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: sleeping function warning from __put_anon_vma
Date: Sun, 1 Jun 2014 21:32:40 +0200 [thread overview]
Message-ID: <20140601193240.GF16155@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.LSU.2.11.1405311321340.10272@eggly.anvils>
On Sat, May 31, 2014 at 01:33:13PM -0700, Hugh Dickins wrote:
> [PATCH] mm: fix sleeping function warning from __put_anon_vma
>
> Trinity reports BUG:
> sleeping function called from invalid context at kernel/locking/rwsem.c:47
> in_atomic(): 0, irqs_disabled(): 0, pid: 5787, name: trinity-c27
> __might_sleep < down_write < __put_anon_vma < page_get_anon_vma <
> migrate_pages < compact_zone < compact_zone_order < try_to_compact_pages ..
>
> Right, since conversion to mutex then rwsem, we should not put_anon_vma()
> from inside an rcu_read_lock()ed section: fix the two places that did so.
>
> Fixes: 88c22088bf23 ("mm: optimize page_lock_anon_vma() fast-path")
> Reported-by: Dave Jones <davej@redhat.com>
> Signed-off-by: Hugh Dickins <hughd@google.com>
> Needs-Ack-from: Peter Zijlstra <peterz@infradead.org>
> ---
>
> mm/rmap.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> --- 3.15-rc7/mm/rmap.c 2014-04-13 17:24:36.680507189 -0700
> +++ linux/mm/rmap.c 2014-05-31 12:02:08.496088637 -0700
> @@ -426,12 +426,14 @@ struct anon_vma *page_get_anon_vma(struc
> * above cannot corrupt).
> */
> if (!page_mapped(page)) {
> + rcu_read_unlock();
> put_anon_vma(anon_vma);
> anon_vma = NULL;
> + goto outer;
> }
> out:
> rcu_read_unlock();
> -
> +outer:
> return anon_vma;
> }
I think we can do that without the goto if we write something like:
if (!page_mapped(page)) {
rcu_read_unlock();
put_anon_vma(anon_vma);
return NULL;
}
> @@ -477,9 +479,10 @@ struct anon_vma *page_lock_anon_vma_read
> }
>
> if (!page_mapped(page)) {
> + rcu_read_unlock();
> put_anon_vma(anon_vma);
> anon_vma = NULL;
> - goto out;
> + goto outer;
> }
>
> /* we pinned the anon_vma, its safe to sleep */
> @@ -501,6 +504,7 @@ struct anon_vma *page_lock_anon_vma_read
>
> out:
> rcu_read_unlock();
> +outer:
> return anon_vma;
> }
Same here too, I suppose.
Interesting that we never managed to hit this one; it might also make
sense to put a might_sleep() in anon_vma_free().
Other than that, I don't see anything really odd, then again, its sunday
evening and my thinking cap isn't exactly on proper.
next prev parent reply other threads:[~2014-06-01 19:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 0:09 sleeping function warning from __put_anon_vma Dave Jones
2014-05-30 0:09 ` Dave Jones
2014-05-31 20:33 ` Hugh Dickins
2014-05-31 20:33 ` Hugh Dickins
2014-05-31 21:04 ` Vlastimil Babka
2014-05-31 21:04 ` Vlastimil Babka
2014-05-31 21:16 ` Hugh Dickins
2014-05-31 21:16 ` Hugh Dickins
2014-06-01 19:32 ` Peter Zijlstra [this message]
2014-06-01 19:32 ` Peter Zijlstra
2014-06-02 9:30 ` Hugh Dickins
2014-06-02 9:30 ` Hugh Dickins
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=20140601193240.GF16155@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.