From: Andreas Dilger <adilger@turbolabs.com>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Jason Thomas <jason@topic.com.au>,
linux-kernel <linux-kernel@vger.kernel.org>,
marcelo@conectiva.com.br
Subject: Re: oops in devfs
Date: Sat, 5 Jan 2002 20:27:15 -0700 [thread overview]
Message-ID: <20020105202715.N12868@lynx.no> (raw)
In-Reply-To: <20020103014507.GB19702@topic.com.au> <200201030724.g037ONj04041@vindaloo.ras.ucalgary.ca> <20020103224744.GB29846@topic.com.au> <200201060047.g060l4p08166@vindaloo.ras.ucalgary.ca>
In-Reply-To: <200201060047.g060l4p08166@vindaloo.ras.ucalgary.ca>; from rgooch@ras.ucalgary.ca on Sat, Jan 05, 2002 at 05:47:04PM -0700
On Jan 05, 2002 17:47 -0700, Richard Gooch wrote:
> Ah! You're using LVM! There are known bugs in LVM which cause memory
> corruptions. I told Heinz about this on 16-DEC, but it appears the CVS
> tree hasn't been updated yet. So grab the latest CVS tree (which fixes
> some bugs) and then apply the appended patch (which fixes more
> bugs). You definately need both. The patch should be applied in the
> drivers/md directory.
Hmm, my understanding was that the LVM CVS already had this patch
applied, but I could be wrong... In any case, I haven't seen anything
about updating the kernel LVM to match CVS since Alan merged in his
-ac LVM code into 2.4.15 or so.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-01-06 3:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 1:45 oops in devfs Jason Thomas
2002-01-03 7:24 ` Richard Gooch
2002-01-03 22:47 ` Jason Thomas
2002-01-06 0:47 ` Richard Gooch
2002-01-06 3:27 ` Andreas Dilger [this message]
2002-01-06 8:32 ` Richard Gooch
2002-01-07 0:39 ` Jason Thomas
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=20020105202715.N12868@lynx.no \
--to=adilger@turbolabs.com \
--cc=jason@topic.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=rgooch@ras.ucalgary.ca \
/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