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]
Message-Id: <200801170915.26040.rusty@rustcorp.com.au>
Date:	Thu, 17 Jan 2008 09:15:25 +1100
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Mathieu SEGAUD <mathieu.segaud@...ala.cx>
Cc:	"rae l" <crquan@...il.com>, open-iscsi@...glegroups.com,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC on MODULE SUPPORT] hello, Rusty, Should we provide module information even if the kernel module compiled built-in with bzImage?

On Wednesday 16 January 2008 22:58:09 Mathieu SEGAUD wrote:
> your userspace program is somewhat broken
> the userspace should not expect to find the version number in
> /sys/module, as this is used by the Linux kernel module subsystem. You
> should provide the required information in another way such as a
> /proc/ file (bad) or a /sys file (better, but no module stuff, this
> has no business with it).

Shh!  He was going to implement a feature we want!

To be honest, I think his expectations of consistency are correct: if a 
version number makes sense, surely it makes sense for builtins as well.

Thanks,
Rusty.
--
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