From: Kyle Rose <krose@krose.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: OOPS at mm/rmap.c:628
Date: Mon, 03 Dec 2007 11:57:45 -0500 [thread overview]
Message-ID: <47543589.3050904@krose.org> (raw)
In-Reply-To: <20071203081243.0a8ad658@laptopd505.fenrus.org>
> Thank you for your report.
> there have been several reports (at least 8 on lkml already) of this
> BUG() before for 2.6.22 (and a few before that), however nobody has
> reported this in 2.6.23 or later, so it's very likely something that
> this got fixed since in a later kernel....
>
Outstanding. That's what I like to hear. (I love it when a plan comes
together?) I anxiously await an Ubuntu 2.6.23-based kernel image. :-)
Kyle
prev parent reply other threads:[~2007-12-03 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 15:30 OOPS at mm/rmap.c:628 Kyle Rose
2007-12-03 16:12 ` Arjan van de Ven
2007-12-03 16:57 ` Kyle Rose [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=47543589.3050904@krose.org \
--to=krose@krose.org \
--cc=arjan@infradead.org \
--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