From: Nick Bowler <nbowler@elliptictech.com>
To: Larry Homes <larr.homes@gmail.com>
Cc: andrew hendry <andrew.hendry@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Possible bug in insmod or the kernel?
Date: Mon, 8 Feb 2010 13:43:38 -0500 [thread overview]
Message-ID: <20100208184338.GA17495@emergent.ellipticsemi.com> (raw)
In-Reply-To: <45c77aec1002081013q2b07cb7flbd827a977ed51d4c@mail.gmail.com>
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/)
next prev parent reply other threads:[~2010-02-08 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 18:56 Larry Homes
2010-02-07 22:14 ` andrew hendry
2010-02-08 18:13 ` Larry Homes
2010-02-08 18:43 ` Nick Bowler [this message]
2010-02-08 18:47 ` Larry Homes
2010-02-09 2:23 ` Américo Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100208184338.GA17495@emergent.ellipticsemi.com \
--to=nbowler@elliptictech.com \
--cc=andrew.hendry@gmail.com \
--cc=larr.homes@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®