From: Andrew Morton <akpm@linux-foundation.org>
To: "Daniel Cid" <dcid@ossec.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] Unable to handle kernel NULL pointer dereference
Date: Mon, 29 Oct 2007 00:42:42 -0700 [thread overview]
Message-ID: <20071029004242.cbf528d0.akpm@linux-foundation.org> (raw)
In-Reply-To: <44003d360710221017k58ce3c2cqb2feff2939b65dae@mail.gmail.com>
On Mon, 22 Oct 2007 14:17:14 -0300 "Daniel Cid" <dcid@ossec.net> wrote:
> Sorry if it isn't the right place to ask this question, but I was
> reported the following error in the kernel.
>
> Syscheckd (process in the crash) is a userland (no kernel/lkm code)
> file integrity checking tool that scans the system and generates the
> md5/sha1 sum of all the files (if it helps to identify the problem).
>
> I am guessing it is a bug in the kernel, since no user process should
> cause this...
>
>
> [root@ss ossec]# uname -a
> Linux ss 2.6.9-55.0.9.ELsmp #1 SMP Thu Sep 27 18:27:41 EDT 2007 i686 i686
> i386 GNU/Linux
>
Sorry, we all stopped thinking about 2.6.9 years ago - unless you're able
to reproduce this on a current kernel (for example, latest Fedora), the
place to report this is https://bugzilla.redhat.com/
Thanks.
next prev parent reply other threads:[~2007-10-29 7:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 17:17 [BUG] Unable to handle kernel NULL pointer dereference Daniel Cid
2007-10-22 17:24 ` Ray Lee
2007-10-29 7:42 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-21 18:32 [BUG] unable " Thomas Meyer
2014-02-15 12:10 John
2014-02-15 20:08 ` John
2014-02-15 20:30 ` Borislav Petkov
2014-02-15 21:04 ` John
2014-02-15 23:25 ` Borislav Petkov
2014-02-16 2:09 ` John
2014-02-16 17:27 ` Trond Myklebust
2014-02-16 17:35 ` Borislav Petkov
2014-02-16 17:35 ` Borislav Petkov
2014-02-17 20:12 ` John
2014-02-17 20:12 ` John
2014-02-17 20:30 ` Borislav Petkov
2014-02-17 20:30 ` Borislav Petkov
2014-02-17 20:35 ` John
2014-02-15 15:19 John
2014-02-17 4:46 Dieter Nützel
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=20071029004242.cbf528d0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dcid@ossec.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.