--- On Sun, 6/27/10, Mulyadi Santosa mulyadi.sant...@gmail.com wrote:
Obviously memory is allocated in both cases.
OK, that was something I was unaware. So, in module A which
originally holds the struct, you already put a value in buf[0]? And
you absolutely sure it's allocated there,
--- On Sat, 6/26/10, Mulyadi Santosa mulyadi.sant...@gmail.com wrote:
From: Mulyadi Santosa mulyadi.sant...@gmail.com
Usman S. Ansari uans...@yahoo.com
wrote:
Don't understand what you are saying.
You said by yourself that kmalloc fixed the situation, right? Actually
it's quite clear once
On Sun, Jun 27, 2010 at 22:36, Usman S. Ansari uans...@yahoo.com wrote:
Obviously memory is allocated in both cases.
OK, that was something I was unaware. So, in module A which originally
holds the struct, you already put a value in buf[0]? And you
absolutely sure it's allocated there, right?
2010/6/26 Mulyadi Santosa mulyadi.sant...@gmail.com:
Dear Usman...
Sorry if I can't give complete explanation, but hopefully it's enough...
On Sat, Jun 26, 2010 at 02:31, Usman S. Ansari uans...@yahoo.com wrote:
I have two kernel modules running.
Module 1:
- struct a
{
int val1;
--- On Fri, 6/25/10, Mulyadi Santosa mulyadi.sant...@gmail.com wrote:
From: Mulyadi Santosa mulyadi.sant...@gmail.com
Subject: Re: Accessing kernel memory from multiple modules
To: Usman S. Ansari uans...@yahoo.com
Cc: Linux Kernel List kernelnewbies@nl.linux.org
Date: Friday, June 25, 2010
On Sun, Jun 27, 2010 at 08:52, Usman S. Ansari uans...@yahoo.com wrote:
Don't understand what you are saying.
You said by yourself that kmalloc fixed the situation, right? Actually
it's quite clear once you think deeper about it (unless I am really
fooled).
Or try using static
--
I have two kernel modules running.
Module 1:
- struct a
{
int val1;
char *buffer
...
};
- Then in module 1, I have following global declaration
struct a buf[20];
- Module 1, calls a exported function module2_function(int *) from modules 2:
it passes buff[0].val1 as a parameter
