From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761843AbZBMH0o (ORCPT ); Fri, 13 Feb 2009 02:26:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761505AbZBMH0b (ORCPT ); Fri, 13 Feb 2009 02:26:31 -0500 Received: from cn.fujitsu.com ([222.73.24.84]:59227 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1761463AbZBMH0a (ORCPT ); Fri, 13 Feb 2009 02:26:30 -0500 Message-ID: <4995208D.8050700@cn.fujitsu.com> Date: Fri, 13 Feb 2009 15:26:05 +0800 From: Li Zefan User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Al Viro CC: containers@lists.osdl.org, Paul Menage , Arjan van de Ven , Andrew Morton , LKML Subject: Re: [cgroup or VFS ?] WARNING: at fs/namespace.c:636 mntput_no_expire+0xac/0xf2() References: <499013CC.2060808@cn.fujitsu.com> <4993BD5D.2020707@cn.fujitsu.com> <20090212062442.GE28946@ZenIV.linux.org.uk> <4993C2A0.3050507@cn.fujitsu.com> <4993C7C2.4060100@cn.fujitsu.com> <20090212070729.GF28946@ZenIV.linux.org.uk> <4995007D.7040101@cn.fujitsu.com> <20090213054751.GI28946@ZenIV.linux.org.uk> <49950F3D.3030704@cn.fujitsu.com> <20090213064135.GJ28946@ZenIV.linux.org.uk> <20090213071816.GK28946@ZenIV.linux.org.uk> In-Reply-To: <20090213071816.GK28946@ZenIV.linux.org.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Al Viro wrote: > On Fri, Feb 13, 2009 at 06:41:35AM +0000, Al Viro wrote: > > Aaaargh... > > /* > * We don't have to hold all of the locks at the > * same time here because we know that we're the > * last reference to mnt and that no new writers > * can come in. > */ > for_each_possible_cpu(cpu) { > struct mnt_writer *cpu_writer = &per_cpu(mnt_writers, cpu); > if (cpu_writer->mnt != mnt) > continue; > spin_lock(&cpu_writer->lock); > > is *almost* OK. Modulo SMP cache coherency. We know that nothing should > be setting ->mnt to ours anymore, that's fine. But we do not know if > we'd seen *earlier* change done on CPU in question (not the one we > are running __mntput() on). > > I probably would still like to use milder solution in the long run, but for > now let's check if turning that into > > struct mnt_writer *cpu_writer = &per_cpu(mnt_writers, cpu); > spin_lock(&cpu_writer->lock); > if (cpu_writer->mnt != mnt) { > spin_unlock(&cpu_writer->lock); > continue; > } > prevents the problem, OK? > Sure, I'll try. :) BTW, thread2's rmdir failed: rmdir: /cgroup/0: No such file or directory