linux-kernel - Re: ISDN testing

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:	Thu, 24 Apr 2008 22:39:07 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Frans Pop <elendil@...net.nl>, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org, isdn4linux@...tserv.isdn4linux.de
Subject: Re: ISDN testing

Andi Kleen wrote:
> Jeff Garzik <jeff@...zik.org> writes:
>> Yeah, that's what my patchset does -- splits the "hisax" driver into
>> multiple smaller drivers.  Thus, "modprobe hisax" produces the results
>> that you are seeing.
> 
> That will break a lot of user's setup.

At present, yes :/  Yet another why it's not upstream :)


>> You'll need to determine which newly-created kernel module applies to
>> your hardware.  Let me know if you need help with that.  The new
>> drivers should be in
>> /lib/modules/2.6.25-isdn/kernel/drivers/isdn/hisax/ provided that you
>> enabled them in the kernel configuration.
> 
> One way to avoid that issue would be to continue having a dummy
> "hisax" module that just depends on all the other drivers with 
> a symbol reference.

I'm definitely open to any solution like this.  Unfortunately (as Frans, 
I think, pointed out) the hisax module routinely depends on critical 
setup info being passed as module options, mainly for non-PCI hardware.

One solution might be to create a dummy hisax module that calls 
foo_module_init() and foo_module_exit(), and stitch them together in an 
unconventional way.

	Jeff



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