From: "Juan J. Quintela" <quintela@fi.udc.es>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: Ooops in filemap_write_page in test8
Date: 11 Sep 2000 17:15:29 +0200 [thread overview]
Message-ID: <ytt3dj7hsdq.fsf@serpe.mitica> (raw)
In-Reply-To: "Petr Vandrovec"'s message of "Mon, 11 Sep 2000 17:06:01 MET-1"
>>>>> "petr" == Petr Vandrovec <VANDROVE@vc.cvut.cz> writes:
petr> On 11 Sep 00 at 17:00, Juan J. Quintela wrote:
>> I was running mmap001 over NFS when I got one Oops, with the
>> following backtrace. The problem is that the page->mapping is
>> NULL, and it causes a NULL access at filemap_write_page.
>> If you need any more info, let me know.
petr> Hi Juan,
petr> is your machine near to VMware or not? I reported same oopses
petr> last week on linux-kernel - they happened after heavy swapped VMware session
petr> on VMware exit (when exit_mmap was cleaning up address space). If you
petr> have idea where mapping gets set to NULL (and why is such page passed
petr> to filemap_write_page), I'd like to know it.
petr> Thanks,
petr> Petr Vandrovec
petr> vandrove@vc.cvut.cz
I don't have vmware here, I am using NFSv3 (kernel NFS). I am
investigating where the page puts ->mapping to NULL. The Oops happend
because a page is in a vma with address operations, but the page
hasn't a mapping :((((
I continue working on that ....
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-09-11 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-11 17:06 Ooops in filemap_write_page in test8 Petr Vandrovec
2000-09-11 15:15 ` Juan J. Quintela [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-11 15:00 Juan J. Quintela
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=ytt3dj7hsdq.fsf@serpe.mitica \
--to=quintela@fi.udc.es \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.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 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.