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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 02 Apr 2008 04:28:51 +0400
From:	Dmitri Vorobiev <dmitri.vorobiev@...il.com>
To:	Johannes Weiner <hannes@...urebad.de>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Fix kernel thread names that might offend users.

Johannes Weiner wrote:
> More and more GNOME users (especially Ubuntu) get confused by their
> process list showing several process names that seem to indicate
> KDE-related services.
> 
> To settle things down a bit on the bugtrackers, this patch renames all
> offending kernel threads into something that goes better with
> GNOME-based systems.
> 
> Since KDE is essentially dead, the thread-names are not made
> compile-time configurable but rather just renamed completely here to
> fit modern distributions. 
> 
> Signed-off-by: Johannes Weiner <hannes@...urebad.de>
> ---
> 
> Please note that these hard-coded names are going to be removed soon
> completely in another patch series that makes kernel thread names more
> `themable' in the sense that users may supply a format string in
> /proc/sys/kernel/kthread_fmt which allows having customizable names
> like "-=[acpid]=-" or similar.
> 
> Also, please let me know if I forgot something. 

Did you forget to send this patch yesterday in which case this would have
been more suitable for April 1st?

Dmitri
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ