[ossec-dev] [Bug 92] Kernel panic after upgrading from 1.2 to 1.3

[ossec-bugzilla@xxxxxxxxxxxxxxxxxxxxxxxxxxx]

http://www.ossec.net/bugs/show_bug.cgi?id=92





------- Comment #2 from risenhoover@xxxxxxxxx  2007-10-20 01:59 -------
(In reply to comment #1)
> Hi Paul,
> 
> Thanks for the bug report, but this is certainly a bug in the Linux Kernel, not
> on OSSEC. Never a user land process (ossec-syscheckd) should cause a NULL
> pointer dereference in the kernel...
> 
> Can you show us you config? What file system are you using? 
> 

I agree with you completely that there is obviously a bug in the Linux kernel,
and that no user land process should ever be able to cause a kernel panic.

If you want to state that the issue is not with OSSEC, fine, but the fact that
ossec-syscheckd shows up in the kernel panic logs indicates otherwise.  Please
explain to me why this isn't *also* a bug in ossec, and I'll go away.

I find it hard to believe that a team of security-conscious individuals would
dismiss my problem out of hand as somebody else's problem, when given evidence
that their product is causing kernel panics.

I submitted this bug to you first, as a courtesy.  If you claim it's not your
problem, fine.  I will begin reporting it to the greater Linux and security
community until somebody takes this issue seriously.


-- 
Configure bugmail: http://www.ossec.net/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.