content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject: module tool with 2.6.9 issue
Date: Thu, 11 Nov 2004 14:27:52 -0700
Message-ID: <08A354A3A9CCA24F9EE9BE13600CFBC50F85CE@wcosmb07.cos.agilent.com>
Thread-Topic: Sparse "context" checking..
Thread-Index: AcTIJiDuaiXLq84HQqubxEnP3IlcIQADwyoA
From: <yiding_wang@agilent.com>
To: <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1235
Lines: 25

I am using moudle-init-tools-3.1-pre6 with kernel 2.6.9. The new insmod seems have restrictions which failed using parameters to load a driver module.

My module parameter is in the form of modname="*************** ****", a quite long one.
Run - insmod modname.o modname="*********** *******" (with a script), it complains about the space and treats the string next to the space to be a "Unknown parameter".

By replacing the space with any character, then it complains 
"modname: string parameter too long"

Reducing the length of the parameter to less than 1k character works fine.

Same long parameter string wit space in between works fine under 2.4.25 with original insmod.

Questions:
1, Is this a bug or new insmod has restrictions? 
2, If it is restriction on special character such as space, or limitation on parameter length, then why and what is the limit? 
3, If insmod has limitation, then what is better way to pass long parameter with some special character? 

Thanks!

Eddie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/