| 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
| ||
|
Date: Mon, 8 Feb 2010 13:47:17 -0500 From: Larry Homes <larr.homes@...il.com> To: Larry Homes <larr.homes@...il.com>, andrew hendry <andrew.hendry@...il.com>, linux-kernel@...r.kernel.org Subject: Re: Possible bug in insmod or the kernel? That was it. The shell was eating the quotes. Thanks alot! On Mon, Feb 8, 2010 at 1:43 PM, Nick Bowler <nbowler@...iptictech.com> wrote: > 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@...ost modules]# insmod hello3.ko name="john smith" >> insmod: error inserting 'hello3.ko': -1 Unknown symbol in module >> >> [root@...ost 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/) > -- 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