All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: "Juan J. Quintela" <quintela@fi.udc.es>
Cc: linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: Ooops in filemap_write_page in test8
Date: Mon, 11 Sep 2000 17:06:01 MET-1	[thread overview]
Message-ID: <6D5D2176666@vcnet.vc.cvut.cz> (raw)

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.

Hi Juan,
  is your machine near to VMware or not? I reported same oopses
last week on linux-kernel - they happened after heavy swapped VMware session
on VMware exit (when exit_mmap was cleaning up address space). If you
have idea where mapping gets set to NULL (and why is such page passed
to filemap_write_page), I'd like to know it.
                                          Thanks,
                                            Petr Vandrovec
                                            vandrove@vc.cvut.cz
                                            
--
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/

             reply	other threads:[~2000-09-11 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-11 17:06 Petr Vandrovec [this message]
2000-09-11 15:15 ` Ooops in filemap_write_page in test8 Juan J. Quintela
  -- 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=6D5D2176666@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=quintela@fi.udc.es \
    /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.