From: Li Zefan <lizf@cn.fujitsu.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: containers@lists.osdl.org, LKML <linux-kernel@vger.kernel.org>,
Paul Menage <menage@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [cgroup or VFS ?] WARNING: at fs/namespace.c:636 mntput_no_expire+0xac/0xf2()
Date: Mon, 16 Feb 2009 09:29:00 +0800 [thread overview]
Message-ID: <4998C15C.2070203@cn.fujitsu.com> (raw)
In-Reply-To: <4995208D.8050700@cn.fujitsu.com>
Li Zefan wrote:
> 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. :)
>
Not a single warning for the whole weekend, so I think above change works.
next prev parent reply other threads:[~2009-02-16 1:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 3:23 [cgroup or VFS ?] WARNING: at fs/namespace.c:636 mntput_no_expire+0xac/0xf2() Li Zefan
2009-02-09 8:40 ` Andrew Morton
2009-02-09 8:49 ` Li Zefan
2009-02-09 11:03 ` Al Viro
2009-02-09 11:58 ` Al Viro
2009-02-10 5:47 ` Li Zefan
2009-02-09 9:34 ` Al Viro
2009-02-09 11:30 ` Li Zefan
2009-02-12 6:10 ` Li Zefan
2009-02-12 6:24 ` Al Viro
2009-02-12 6:33 ` Li Zefan
2009-02-12 6:54 ` Li Zefan
[not found] ` <4993C7C2.4060100-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2009-02-12 7:07 ` Al Viro
2009-02-12 7:07 ` Al Viro
2009-02-13 5:09 ` Li Zefan
[not found] ` <4995007D.7040101-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2009-02-13 5:47 ` Al Viro
2009-02-13 5:47 ` Al Viro
2009-02-13 6:12 ` Li Zefan
2009-02-13 6:31 ` Li Zefan
[not found] ` <49950F3D.3030704-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2009-02-13 6:41 ` Al Viro
2009-02-13 6:41 ` Al Viro
2009-02-13 7:18 ` Al Viro
[not found] ` <20090213071816.GK28946-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2009-02-13 7:26 ` Li Zefan
2009-02-13 7:26 ` Li Zefan
2009-02-16 1:29 ` Li Zefan [this message]
2009-02-16 2:38 ` Al Viro
2009-02-16 2:47 ` Li Zefan
2009-02-16 2:57 ` Al Viro
2009-02-09 17:48 ` Dave Hansen
2009-02-09 18:11 ` Arjan van de Ven
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=4998C15C.2070203@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=containers@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=viro@ZenIV.linux.org.uk \
/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.