From: Daniel Walker <dwalker@mvista.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@elte.hu, paulmck@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH] release quicklist before free_page
Date: Mon, 23 Jul 2007 09:26:19 -0700 [thread overview]
Message-ID: <1185207979.2573.55.camel@imap.mvista.com> (raw)
In-Reply-To: <1185208378.8197.20.camel@twins>
On Mon, 2007-07-23 at 18:32 +0200, Peter Zijlstra wrote:
> On Mon, 2007-07-23 at 08:21 -0700, Daniel Walker wrote:
> > Resolves,
> >
> > BUG: sleeping function called from invalid context cc1(29651) at kernel/rtmutex.c:636
> > in_atomic():1 [00000001], irqs_disabled():0
> > [<c0119f50>] __might_sleep+0xf3/0xf9
> > [<c031600e>] __rt_spin_lock+0x21/0x3c
> > [<c014102c>] get_zone_pcp+0x20/0x29
> > [<c0141a40>] free_hot_cold_page+0xdc/0x167
> > [<c013a3f4>] add_preempt_count+0x12/0xcc
> > [<c0110d92>] pgd_dtor+0x0/0x1
> > [<c015d865>] quicklist_trim+0xb7/0xe3
> > [<c0111025>] check_pgt_cache+0x19/0x1c
> > [<c0148df5>] free_pgtables+0x54/0x12c
> > [<c013a3f4>] add_preempt_count+0x12/0xcc
> > [<c014e5be>] unmap_region+0xeb/0x13b
> >
> >
> > It looks like the quicklist isn't used after a few variables are evaluated.
> > So no need to keep preemption disabled over the whole function.
>
> Not quite, it uses preempt_disable() to avoid migration and stick to a
> cpu. Without that it might end up freeing pages from another quicklist.
>
> How about this - compile tested only
How about a comment to go with it ? Which says something like what's
above, notes on how the locking is getting used..
Daniel
next prev parent reply other threads:[~2007-07-23 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 15:21 Daniel Walker
2007-07-23 16:32 ` Peter Zijlstra
2007-07-23 16:26 ` Daniel Walker [this message]
2007-07-23 18:23 ` Ingo Molnar
2007-07-23 18:27 ` Daniel Walker
2007-07-23 18:58 ` Ingo Molnar
2007-07-23 19:46 ` Daniel Walker
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=1185207979.2573.55.camel@imap.mvista.com \
--to=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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 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®