Re: [PATCH][BUGFIX] memcg: fix for deadlock betweenlock_page_cgroup and mapping tree_lock

From: nishimura
Date: Wed May 13 2009 - 00:16:21 EST


> On Wed, 13 May 2009 09:32:50 +0900
> KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote:
>
>> On Wed, 13 May 2009 09:28:28 +0900
>> Daisuke Nishimura <nishimura@xxxxxxxxxxxxxxxxx> wrote:
>>
>> > On Wed, 13 May 2009 08:59:49 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote:
>> > > On Tue, 12 May 2009 19:58:23 +0900
>> > > Daisuke Nishimura <d-nishimura@xxxxxxxxxxxxxxxxx> wrote:
>> > >
>> > > > On Tue, 12 May 2009 17:13:56 +0900
>> > > > KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote:
>> > > >
>> > > > > On Tue, 12 May 2009 17:00:07 +0900
>> > > > > Daisuke Nishimura <nishimura@xxxxxxxxxxxxxxxxx> wrote:
>> > > > > > hmm, I see.
>> > > > > > cache_charge is outside of tree_lock, so moving uncharge would make sense.
>> > > > > > IMHO, we should make the period of spinlock as small as possible,
>> > > > > > and charge/uncharge of pagecache/swapcache is protected by page lock, not tree_lock.
>> > > > > >
>> > > > > How about this ?
>> > > > Looks good conceptually, but it cannot be built :)
>> > > >
>> > > > It needs a fix like this.
>> > > > Passed build test with enabling/disabling both CONFIG_MEM_RES_CTLR
>> > > > and CONFIG_SWAP.
>> > > >
>> > > ok, will update. can I add you Signed-off-by on the patch ?
>> > >
>> > Sure.
>> >
>> > Signed-off-by: Daisuke Nishimura <nishimura@xxxxxxxxxxxxxxxxx>
>> >
>> > The patch(with my fix applied) seems to work fine, I need run it
>> > for more long time though.
>> >
>> Ok, I'll treat this as an independent issue, not as "4/4".
>>
> Could you merge mine and yours and send it to Andrew ?
> I think this is a fix for dead-lock and priority is very high.
> I foumd my system broken and installing the whole system again, now.
> So, I can't post patch today.
>
Okey.

I'll post it soon.

Thanks,
Daisuke Nishimura.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/