From: "Gabriel A. Devenyi" <ace@staticwave.ca>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OOPS] nfsv4 in linux 2.6.13 (-ck7)
Date: Wed, 12 Oct 2005 19:37:55 -0400 [thread overview]
Message-ID: <200510121937.55434.ace@staticwave.ca> (raw)
In-Reply-To: <20051012233159.GJ5856@shell0.pdx.osdl.net>
On October 12, 2005 19:31, Chris Wright wrote:
> In this case it's not very likely since others are seeing same problem
> under load. However, a binary module can corrupt any kernel memory.
> So as a general rule all bets are off with a binary module loaded.
Thanks, I'll keep that in mind for next time. With regards to the patch in the other thread,
should I try and patch the client, the server or both?
--
Gabriel A. Devenyi
ace@staticwave.ca
next prev parent reply other threads:[~2005-10-12 23:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 23:03 [OOPS] nfsv4 in linux 2.6.13 (-ck7) Gabriel A. Devenyi
2005-10-12 23:24 ` Chris Wright
2005-10-12 23:27 ` Gabriel A. Devenyi
2005-10-12 23:31 ` Chris Wright
2005-10-12 23:37 ` Gabriel A. Devenyi [this message]
2005-10-12 23:56 ` Chris Wright
2005-10-14 14:05 ` Gabriel A. Devenyi
2005-10-14 18:13 ` Chris Wright
2005-10-14 15:49 ` Trond Myklebust
2005-10-15 17:23 ` Gabriel A. Devenyi
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=200510121937.55434.ace@staticwave.ca \
--to=ace@staticwave.ca \
--cc=chrisw@osdl.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