linux-kernel - Re: [PATCH] get rid of [softirq-NULL]

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] [day] [month] [year] [list]

Message-ID: <4de7f8a60909250116o69a52b09wbbeec340de4b7158@mail.gmail.com>
Date:	Fri, 25 Sep 2009 10:16:22 +0200
From:	Jan Blunck <jblunck@...e.de>
To:	Remy Bohmer <linux@...mer.net>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: [PATCH] get rid of [softirq-NULL]

On Thu, Sep 24, 2009 at 10:43 PM, Remy Bohmer <linux@...mer.net> wrote:
> if CONFIG_HIGH_RES_TIMERS is not configured, still the hrtimer-softirq
> is started, so to prevent the name 'softirq-NULL' in 'ps' output we
> should still define its name here.
> Preventing the softirq from starting at all would touch much more code, so
> I chose the easy way here, it is a cosmetic fix anyway.

Anyway, it would be the right thing to do just that.

Just un-define the enum HRTIMER_SOFTIRQ and the code that needs
modification should pop up. Removing it from the enum also disables
the kthread. Most of the code that raises the softirq should be
guarded by CONFIG_HIGH_RES_TIMERS anyway.

HtH,
Jan
--
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/