From: Joshua Kwan <joshk@triplehelix.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [vma list corruption] Re: proc_pid_readlink oopses again on 2.6.14.5
Date: Thu, 29 Dec 2005 21:53:06 -0800 [thread overview]
Message-ID: <43B4CB42.7050603@triplehelix.org> (raw)
In-Reply-To: <1135758794.2935.3.camel@laptopd505.fenrus.org>
Gentlemen,
On 12/28/2005 12:33 AM, Arjan van de Ven wrote:
>>So you've got 0xb7c1fc20 as vma. Which is not good, since that's a userland
>>address.
>
>
> sounds like it may also be a good idea to check for rootkits; some of
> those try to muck with the vma chains and stuff.... and break if the
> kernel changes a bit.
I rebuilt the SAME kernel source (2.6.14.5) with gcc-3.3, and everything
works fine.
Still rootkit, GCC's problem, or what?
Thanks.
--
Joshua Kwan
next prev parent reply other threads:[~2005-12-30 5:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-28 5:52 proc_pid_readlink oopses again on 2.6.14.5 Joshua Kwan
2005-12-28 6:53 ` [vma list corruption] " Al Viro
2005-12-28 7:24 ` Joshua Kwan
2005-12-28 8:33 ` Arjan van de Ven
2005-12-30 5:53 ` Joshua Kwan [this message]
2005-12-28 8:52 ` Arjan van de Ven
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=43B4CB42.7050603@triplehelix.org \
--to=joshk@triplehelix.org \
--cc=arjan@infradead.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