Yup perfect and understood..
Thanks,
-Pradeep
On Tue, Sep 14, 2010 at 7:32 PM, Venkatram Tummala
wrote:
> On Tue, Sep 14, 2010 at 4:24 PM, Pradeep Shetty
> wrote:
>
>> Once I have initialized crypt_sys with crypt while loading the module,
>> isn't that my user code should call sys_crypt_sys an
Once I have initialized crypt_sys with crypt while loading the module, isn't
that my user code should call sys_crypt_sys and not any of crypt_sys or
crypt? Just got confused with your last statement..
Thanks & Regards,
-Pradeep
On Tue, Sep 14, 2010 at 7:14 PM, Venkatram Tummala
wrote:
> On Tue,
On Tue, Sep 14, 2010 at 4:04 PM, Pradeep Shetty wrote:
> Thanks Venkatram...
>
> I'll probably use the first one as I had similar approach in my mind but
> didn't know whether it was possible though its not the best approach.
>
> So, basically I need to add 2 things in kernel.. A wrapper function
Thanks Venkatram...
I'll probably use the first one as I had similar approach in my mind but
didn't know whether it was possible though its not the best approach.
So, basically I need to add 2 things in kernel.. A wrapper function with a
null function pointer and a system call which ends up calli
On Tue, Sep 14, 2010 at 2:40 PM, Pradeep Shetty wrote:
> Hello,
>
> I learnt that the sys_call_table is no longer is exportable in 2.6+. I'm
> using 2.6.35.4 and trying to implement it in a LKM. I read the virtual addr
> of sys_call_table from the system map and made its physical page writable
> a
