From: Hugh Dickins <hughd@google.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Dave Jones <davej@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
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: Sat, 31 May 2014 14:16:55 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.11.1405311411420.1125@eggly.anvils> (raw)
In-Reply-To: <538A43E0.5070706@suse.cz>
On Sat, 31 May 2014, Vlastimil Babka wrote:
> On 05/31/2014 10:33 PM, Hugh Dickins wrote:
> > On Thu, 29 May 2014, Dave Jones wrote:
> >
> >> BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:47
> >> in_atomic(): 0, irqs_disabled(): 0, pid: 5787, name: trinity-c27
> >> Preemption disabled at:[<ffffffff990acc7e>] vtime_account_system+0x1e/0x50
>
> Just wondering, since I'm not familiar with this kind of bug, is the line above
> bogus or what does it mean? I don't see how the stack trace or the fix patch is
> related to vtime_account_system?
I know no more about it than you do, never noticed such a message before,
and clearly not helpful here. I expect it's like those "last sysfs file"
messages, occasionally useful but mostly noise.
Hugh
--
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>
next prev parent reply other threads:[~2014-05-31 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 0:09 Dave Jones
2014-05-31 20:33 ` Hugh Dickins
2014-05-31 21:04 ` Vlastimil Babka
2014-05-31 21:16 ` Hugh Dickins [this message]
2014-06-01 19:32 ` Peter Zijlstra
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=alpine.LSU.2.11.1405311411420.1125@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=vbabka@suse.cz \
/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