information required

information required

[info]

Thanks for your last email response to me.
The information required should include the following-:
Your full names
Your address
Telephone number
Your private email
Occupation
Age
This is to enable my further discussion with you in confidence.
Best regards and wishes to you.
Mohammad Amir Khadov

NB: Please reply to:

uk4uk@postaxte.com


uk3uk@postaxte.com

information required

[info at 3guneurope.eu]

Thanks for your last email response to me.
The information required should include the following-:
Your full names
Your address
Telephone number
Your private email
Occupation
Age
This is to enable my further discussion with you in confidence.
Best regards and wishes to you.
Mohammad Amir Khadov

NB: Please reply to:

uk4uk at postaxte.com


uk3uk at postaxte.com
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

information required

[.Moh Khadov]

-- 
=============================================
Thanks for your last email response to me.
The information required should include the following-:
Your full names
Your address
Telephone number
Your private email
Occupation
Age
This is to enable my further discussion with you in confidence.
Best regards and wishes to you.
Mohammad Amir Khadov

NB: Please reply to:

uk6uk@postaxte.com


uk5uk@postaxte.com

information required

[info]

Thanks for your last email response to me.
The information required should include the following-:
Your full names
Your address
Telephone number
Your private email
Occupation
Age
This is to enable my further discussion with you in confidence.
Best regards and wishes to you.
Mohammad Amir Khadov

NB: Please reply to:

uk4uk@postaxte.com


uk3uk@postaxte.com

RE: Information required

[Adeel Malik]

[-- Attachment #1: Type: text/plain, Size: 2770 bytes --]

Hello Jun,

Thanks for the reply.I have checked for the unresolved function symbols like
"printk" and "register_chrdev", and found that they are present in
/proc/ksyms. So it appears to me that I may be compiling the module with
incorrect parameters.

Below is the Makefile for the Loadable Module:

/***************************************************************************
**************************************/

CROSS_COMPILE=
/backup/buildroot-QuickMIPS/build/staging_dir/bin/mipsel-uclibc-

TARGET = example_driver

INCLUDE = /backup/buildroot-QuickMIPS/build/linux-2.4.20/include

CC = $(CROSS_COMPILE)gcc -I${INCLUDE}

CFLAGS = -DMODVERSIONS -I${INCLUDE}/linux/modversions.h

${TARGET}.o: ${TARGET}.c

.PHONY: clean

clean:

rm -rf ${TARGET}.o

/***************************************************************************
*************************************/

Do you think that I need to modify the makefile or add some more options to
CFLAGS.

I have ensured that the kernel is compiled with "module-option" turned on.

Also my module uses symbol versioning (sometimes called module versioning).

I use the following lines of code at the start of header file to accomplish
this:

/***************************************************************************
**********************************/

#if defined (CONFIG_MODVERSIONS) && ! defined (MODVERSIONS)

#include <linux/modversions.h>

#define MODVERSIONS

#endif

/***************************************************************************
**********************************/

I have successfully cross-compiled user-space applications on the target
platform. Only when i do the kernel work, this unresolved symbol (like
printk, register_chrdev, etc..) phenomenon happens.

ADEEL MALIK,

 

-----Original Message-----

From: linux-mips-bounce@linux-mips.org

[mailto:linux-mips-bounce@linux-mips.org]On Behalf Of Jun Sun

Sent: Wednesday, August 27, 2003 9:51 PM

To: Adeel Malik

Cc: linux-mips@linux-mips.org; jsun@mvista.com

Subject: Re: Information required

 

On Wed, Aug 27, 2003 at 07:30:26PM +0500, Adeel Malik wrote:

> Hi All,

> I am involved in Embedded Linux Development for MIPS Processor. I

> need to write a device driver for a MIPS Target Platform. When I insmod
the

> driver.o file, the linux bash script running on the target hardware gives
me

> the error message like ;

> 1. unable to resolve the printk function

> 2. unable to resolve the register_chardev function

> etc.

> Can you plz give me the direction as to how to proceed to tackle this

> situation.

Make sure your kernel compiled with module option turned on.

Does it use module version (CONFIG_MODVERSIONS)?

If so, add -DMODVERSIONS -include $(KERNEL_PATH)/include/linux/modversions.h

to your CFLAGS.

Jun

 


[-- Attachment #2: Type: text/html, Size: 3456 bytes --]

Re: Information required

[Jun Sun]

On Wed, Aug 27, 2003 at 07:30:26PM +0500, Adeel Malik wrote:
> Hi All,
>            I am involved in Embedded Linux Development for MIPS Processor. I
> need to write a device driver for a MIPS Target Platform. When I insmod the
> driver.o file, the linux bash script running on the target hardware gives me
> the error message like ;
> 1. unable to resolve the printk function
> 2. unable to resolve the register_chardev function
> etc.
> Can you plz give me the direction as to how to proceed to tackle this
> situation.

Make sure your kernel compiled with module option turned on.
Does it use module version (CONFIG_MODVERSIONS)?
If so, add -DMODVERSIONS -include $(KERNEL_PATH)/include/linux/modversions.h
to your CFLAGS.

Jun

Information required

[Adeel Malik]

[-- Attachment #1: Type: text/plain, Size: 481 bytes --]

Hi All,
           I am involved in Embedded Linux Development for MIPS Processor. I
need to write a device driver for a MIPS Target Platform. When I insmod the
driver.o file, the linux bash script running on the target hardware gives me
the error message like ;
1. unable to resolve the printk function
2. unable to resolve the register_chardev function
etc.
Can you plz give me the direction as to how to proceed to tackle this
situation.
Regards,
 
ADEEL MALIK,
Design Engineer

[-- Attachment #2: Type: text/html, Size: 1780 bytes --]

Re: Information required

[Jesse Pollard]

On Thursday 23 January 2003 08:06 am, Rashmi Agrawal wrote:
> Hi All,
>
> I am developing a software which require very high performance for data
> store/retrieval. Taking that into consideration, I decided to go for kernel
> space system calls for read/write, open/close etc.

most likely a real time application? However, there are no system calls
within the kernel. Only between user mode and kernel mode.

> I directly calls the file operation from within the kernel. Since kernel
> has access to all system resources and low level hardware, could somebody
> point out if it is secure enough to read/write in kernel space.

No.

> If it is not advisable directly to use system calls in kernel, can we do
> something to make it secure?? or do we already have something which
> provides us security even if I do kernel space system call implementation.

Can't be done. You already acknowleged that the kernel has access to all 
system resources and low level hardware, you should realize that any 
protection put in place is already bypassed by the application.

-- 
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Information required

[Rashmi Agrawal]

[-- Attachment #1.1: Type: text/plain, Size: 811 bytes --]

Hi All,

I am developing a software which require very high performance for data store/retrieval. Taking that into consideration, I decided to go for kernel space system calls for read/write, open/close etc. 

I directly calls the file operation from within the kernel. Since kernel has access to all system resources and low level hardware, could somebody point out if it is secure enough to read/write in kernel space.

If it is not advisable directly to use system calls in kernel, can we do something to make it secure?? or do we already have something which provides us security even if I do kernel space system call implementation.

Any information provided on this would be useful. Also problems faced with this kind of implementation will give me more clarity on what to do.

Regards
Rashmi

[-- Attachment #1.2: Type: text/html, Size: 1217 bytes --]

[-- Attachment #2: Wipro_Disclaimer.txt --]
[-- Type: text/plain, Size: 522 bytes --]

**************************Disclaimer**************************************************    
 
 Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' 
and 'confidential' and intended for use only by the individual or entity to which it is 
addressed. You are notified that any use, copying or dissemination of the information 
contained in the E-MAIL in any manner whatsoever is strictly prohibited.

****************************************************************************************