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]
Date:	Tue, 28 Jul 2009 22:23:38 -0700
From:	Greg KH <greg@...ah.com>
To:	Tomas Carnecky <tom@...ervice.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Show module version sysfs file for built-in modules?

On Fri, Jul 24, 2009 at 09:08:51PM +0200, Tomas Carnecky wrote:
> Some userspace tools check /sys/modules/XYZ/version to determine  
> whether the required module is available and the version compatible  
> with the userspace tool. But that sysfs file is not shown when the  
> module is built into the kernel (as opposed being a loadable module).  
> Is there a reason for that behavior? Or is there another way for  
> userspace to check the presence and version of a module?
> The userspace tool in question here is the open-iscsi daemon (iscsid)  
> which checks /sys/modules/scsi_transport_iscsi/version and refuses to  
> start if that file doesn't exist.

A patch to fix this would probably be gladly accepted.

thanks,

greg k-h
--
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