linux-kernel - Re: [RFC][PATCH 0/1] MAZE: Mazed processes monitor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 22 May 2008 18:31:12 +0900
From:	Hirofumi Nakagawa <hnakagawa@...aclelinux.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	linux-kernel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>
Subject: Re: [RFC][PATCH 0/1] MAZE: Mazed processes monitor

Hi Andrew,

Thank you for your comment and review.

> The immediate quesstion is, of course, "why does this need to be done
> in-kernel?".  I am unable to answer that from the provided changelog
> information, and I should be able to do that.

It needs to be done in kernel because excessive CPU cycle usage
is directly detected watching kernel internal task_struct.state.
It's hard to get that information outside the kernel.

Additionally, this patch's aim is to implement a
CGL (Carrier Grade Linux) requirement (AVL.14.0).

There are specs that can not be implemented outside the kernel.
These are;
  - Communication between the monitoring process and the kernel
  - Ability to define policy based on process events including
    process/thread creation and exit, and,
  - Ability to set the CPU cycle threshold to a resolution of
    one millisecond.

Thanks.
Hirofumi Nakagawa


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/