From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Willy Tarreau <w@1wt.eu>
Cc: Jan Engelhardt <jengelh@medozas.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: bad pmd ffff810000207808(9090909090909090).
Date: Wed, 07 May 2008 08:06:47 +0900 [thread overview]
Message-ID: <87abj3nibc.fsf@duaron.myhome.or.jp> (raw)
In-Reply-To: <20080506195014.GS8474@1wt.eu> (Willy Tarreau's message of "Tue, 6 May 2008 21:50:15 +0200")
Willy Tarreau <w@1wt.eu> writes:
>> I see. I'm not sure, but I didn't notice this soon, maybe it worked as
>> almost usual.
>
> I got immediate same feeling as Jan here. It looks very much like someone
> has tried to inject code into your system. The problem is that you don't
> know if this finally succeeded. Maybe some backdoor is now installed in
> your kernel. If I were you, I would isolate the machine, reboot it on CD
> and check MD5s (particularly the ones of the kernel and modules) before
> rebooting it.
Hm.. I've checked md5sum as far as I can do (/var/lib/dpkg/info/*.md5sums).
It seems to have no difference except data files.
And this machine is in back of firewall of other machine, and the kernel
is builded from source each every day or a hour or such.
So, it is unlikely...
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-05-06 23:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 12:00 OGAWA Hirofumi
2008-05-06 12:35 ` Jan Engelhardt
2008-05-06 12:52 ` OGAWA Hirofumi
2008-05-06 19:50 ` Willy Tarreau
2008-05-06 23:06 ` OGAWA Hirofumi [this message]
2008-05-06 23:21 ` Willy Tarreau
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=87abj3nibc.fsf@duaron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=w@1wt.eu \
/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