From: Andrea Arcangeli <andrea@suse.de>
To: Marcello Barnaba <l.barnaba@openssl.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-aa1: Badness in __remove_from_page_cache at mm/filemap.c:104 && page_remove_rmap at mm/objrmap.c:379
Date: Sun, 4 Apr 2004 21:15:20 +0200 [thread overview]
Message-ID: <20040404191520.GA482@dualathlon.random> (raw)
In-Reply-To: <1081103153.13362.21.camel@nowhere.openssl.softmedia.lan>
On Sun, Apr 04, 2004 at 08:25:53PM +0200, Marcello Barnaba wrote:
> Hi Andrea,
>
> I've just installed 2.6.5-aa1, and after some hours of uptime and
> testing, with everything working properly, I experienced some WARN_ON()
> triggered (my syslog became quite big :).
>
> I've got both the nvidia and vmware modules installed.
>
> The bug is fully reproducible, you just have to suspend a virtual
> machine from the vmware GUI, vmware-vmx starts using 100%CPU (just one
> in my 2-way SMP system), and the syslog is completely _filled_ with call
> traces:
>
> vjt@nowhere:~$ grep Badness.in.page.remove.rmap /var/log/syslog | wc -l
> 8859
> vjt@nowhere:~$ grep Badness.in.__remove_from_pa /var/log/syslog | wc -l
> 8767
>
> And here there are two of them (they are all identical).
> First occur the 8700 __remove_from_page_cache() warnings, and then the
> page_remove_rmap() ones.
that's an xfs bug found by Andrew, it started to be visible in -aa
because of the objrmap hardness checks from Dave. You can safely ignore
it, the xfs folks are already testing a fix. I didn't delete the WARN_ON
because it's a race condition we want to trap, but you can go ahead and
delete by hand mm/filemap.c:104 and mm/objrmap.c:379 if you're annoyed
by these warning messages. Kernel will work as stable as mainline
despite of the warnings.
prev parent reply other threads:[~2004-04-04 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 18:25 2.6.5-aa1: Badness in __remove_from_page_cache at mm/filemap.c:104 && page_remove_rmap at mm/objrmap.c:379 Marcello Barnaba
2004-04-04 19:15 ` Andrea Arcangeli [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=20040404191520.GA482@dualathlon.random \
--to=andrea@suse.de \
--cc=l.barnaba@openssl.it \
--cc=linux-kernel@vger.kernel.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