Messages in this thread | | | Date | Mon, 8 Feb 2010 13:43:38 -0500 | From | Nick Bowler <> | Subject | Re: Possible bug in insmod or the kernel? |
| |
On 13:13 Mon 08 Feb , Larry Homes wrote: > No, the problem is not that the quotes are showing. The problem is > that as soon as it sees a space, it assumes the following is the next > parameters name. So for example: > > [root@myhost modules]# insmod hello3.ko name="john smith" > insmod: error inserting 'hello3.ko': -1 Unknown symbol in module > > [root@myhost modules]# insmod hello3.ko "name=john smith" > insmod: error inserting 'hello3.ko': -1 Unknown symbol in module > > In both cases, dmesg shows: > > hello3: Unknown parameter `smith' > > I looked at the params.c code and it seems like the above should work.
I'm not familiar with the code in question, but I suspect that it expects to actually see the quotation marks in the parameter value, but your shell is eating them. Try
insmod hello3.ko 'name="john smith"'
instead.
-- Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
| |