From: Chip Salzenberg <chip@debian.org>
To: Joel Soete <jsoe0708@tiscali.be>
Cc: parisc-linux@lists.parisc-linux.org, 201873-done@bugs.debian.org
Subject: [parisc-linux] Re: Bug#201873: nfs-kernel-server: can't use nfs ...
Date: Fri, 25 Jul 2003 11:49:23 -0400 [thread overview]
Message-ID: <20030725154923.GR2287@perlsupport.com> (raw)
In-Reply-To: <3F1CEEEE000003DF@ocpmta8.freegates.net>
According to Joel Soete:
> dmesg informe me that rpc.mountd do_page_fault() at this very moment
This is almost certainly the use-of-freed-memory bug that many people
suffered from in 1.0.3-1.
I have already uploaded 1.0.5-1, which fixes this bug, so I'm closing
this bug report. If your problem continues to occur (which I strongly
doubt it will), please submit a new bug.
Thanks for the bug report.
--
Chip Salzenberg - a.k.a. - <chip@pobox.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
but he stepped in a wormhole and had to go in early." // MST3K
prev parent reply other threads:[~2003-07-25 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 13:01 [parisc-linux] nfs-kernel-server: can't use nfs Joel Soete
2003-07-25 15:49 ` Chip Salzenberg [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=20030725154923.GR2287@perlsupport.com \
--to=chip@debian.org \
--cc=201873-done@bugs.debian.org \
--cc=jsoe0708@tiscali.be \
--cc=parisc-linux@lists.parisc-linux.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