linux-kernel - Re: Unneeded kernel threads (xfs, jfs, gfs2)

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:	Tue, 13 May 2008 11:30:59 +0300
From:	Georgi Chorbadzhiyski <gf@...xsol.org>
To:	Donald Douwsma <donaldd@....com>
CC:	xfs@....sgi.com, jfs-discussion@...ts.sourceforge.net,
	cluster-devel@...hat.com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Unneeded kernel threads (xfs, jfs, gfs2)

Donald Douwsma mumbled something about, On 5/13/08 8:29 AM:
> Georgi Chorbadzhiyski wrote:
>> Hi guys, I know that not all kernel thread users are converted to
>> start only when needed but the following is little annoying specially
>> when I'm not even using jfs, xfs and gfs2.
>>
>> Look at the ps output from a standard distro 2.6.24.5 kernel after a
>> fresh boot:
> ...
> 
>> Kernel config can be found here:
>>   
>> http://mirrors.unixsol.org/slackware/slackware-12.1/kernels/hugesmp.s/config 
> 
> Your distro is building all of these modules into the kernel.
>     CONFIG_XFS_FS=y
>     CONFIG_JFS_FS=y
>     CONFIG_GFS2_FS=y
> 
> This isnt exactly standard practice, normally they'd be set to =m and only
> used if required to mount a filesystem. You may want to ask the slackware
> people why they chose to do this for their hugexxx.s kernels.

I know that they are compiled in the kernel, but since they
are not used isn't starting their own kthreads kind of
unnecessary? Surely the threads can be started on demand
only when xfs/etc volume is mounted.

-- 
Georgi Chorbadzhiyski
http://georgi.unixsol.org/

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