From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: vm related lock up in 2.6.15
Date: Mon, 9 Jan 2006 11:35:07 -0500 [thread overview]
Message-ID: <20060109163507.GA20205@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0601090830040.3169@g5.osdl.org>
On Mon, Jan 09, 2006 at 08:32:20AM -0800, Linus Torvalds wrote:
> > Turns out this was your BUG_ON(page_count(p) <= page_mapcount(p));
> > addition to putpage_test_zero, which I added a few days ago and promptly
> > forgot about.
> >
> > Triggering this isn't too difficult it seems :-/
>
> Well, as I warned in the message that had the patch, the test _is_ racy.
> The reads of the page counts have no serialization, so if another process
> is changing them, I don't guarantee that the test is correct.
>
> IOW, it was meant as a special case debug test for one particular problem
> where I hoped it would give more information, rather than a real patch.
ok, that explains. I'll go back to chasing the real cause of the corruption
I was seeing :-/
Dave
prev parent reply other threads:[~2006-01-09 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 2:12 vm related lock up in 2.6.15 Dave Jones
2006-01-09 15:49 ` Dave Jones
2006-01-09 16:32 ` Linus Torvalds
2006-01-09 16:35 ` Dave Jones [this message]
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=20060109163507.GA20205@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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