Re: Include path for module compilation

2009-03-10 Thread Harsha
On Tue, Mar 10, 2009 at 12:02 AM, Vishal Thanki wrote: > yea.. its defined as "extern" there.. and no, don't include ".c" file :) > i believe that ur kernel is not built with timekeeping.o.. > can you send me the output of "cat /proc/kallsyms  | grep xtime" command ?? [r...@localhost host-tests]#

Re: any NX memory areas?

2009-03-10 Thread NAHieu
On Wed, Mar 11, 2009 at 1:22 PM, NAHieu wrote: > Thanks for all the links, but that is not what I am looking for. > > My question is: I dont understand why some (all?) data areas in my > NX-enable machine dont prohibit execution (why it should). I mean "(while it should)" above (not "why") Thank

Re: any NX memory areas?

2009-03-10 Thread NAHieu
Thanks for all the links, but that is not what I am looking for. My question is: I dont understand why some (all?) data areas in my NX-enable machine dont prohibit execution (why it should). I dont look for the solution (like PaX), just want to know why NX-feature doesnt behave like I expected.

Re: any NX memory areas?

2009-03-10 Thread Peter Teoh
Sorry, and another article too: Bypassing PaX ASLR protection On Wed, Mar 11, 2009 at 11:55 AM, Peter Teoh wrote: > Bypassing PaX - check out this Phrack article: > > The advanced return-into-lib(c) exploits > > On Wed, Mar 11, 2009 at 11:51 AM, Peter Teoh wrote: >> the best I can find is this:

Re: any NX memory areas?

2009-03-10 Thread Peter Teoh
Bypassing PaX - check out this Phrack article: The advanced return-into-lib(c) exploits On Wed, Mar 11, 2009 at 11:51 AM, Peter Teoh wrote: > the best I can find is this: > > http://wapedia.mobi/en/Executable_space_protection > > which indicated that ExecShield was rejected because of some > "in

Re: any NX memory areas?

2009-03-10 Thread Peter Teoh
the best I can find is this: http://wapedia.mobi/en/Executable_space_protection which indicated that ExecShield was rejected because of some "intrusive changes". And reading this: http://wapedia.mobi/en/Exec_Shield ExecShield is only an emulation, not really requiring true hardware support, an

Re: any NX memory areas?

2009-03-10 Thread Pei Lin
i think if date area can execute code ,it is really very dangerous for cracker who can easily write shellcode like : char shellcode[]={}; void (*fp)() = shellcode; fp(); these some virus lovers give examples: http://www.governmentsecurity.org/forum/lofiversion/index.php/t31130.html I search on t

Re: any NX memory areas?

2009-03-10 Thread Peter Teoh
It has been done before - called PaX.   Search the Phrack article on PaX. On Wed, Mar 11, 2009 at 10:04 AM, NAHieu wrote: > > On Wed, Mar 11, 2009 at 10:46 AM, NAHieu wrote: > > On Tue, Mar 10, 2009 at 4:13 PM, Peter Teoh wrote: > >> Sorry, my mistake, PAE is required yes, and then 32bit Linux

Re: any NX memory areas?

2009-03-10 Thread NAHieu
On Wed, Mar 11, 2009 at 10:46 AM, NAHieu wrote: > On Tue, Mar 10, 2009 at 4:13 PM, Peter Teoh wrote: >> Sorry, my mistake, PAE is required yes, and then 32bit Linux Kernel >> will have NX enabled: >> >> PAE can be enabled with CONFIG_X86_PAE (and CONFIG_HIGHMEM64G - >> possibly needed, which is w

Re: any NX memory areas?

2009-03-10 Thread NAHieu
On Tue, Mar 10, 2009 at 4:13 PM, Peter Teoh wrote: > Sorry, my mistake, PAE is required yes, and then 32bit Linux Kernel > will have NX enabled: > > PAE can be enabled with CONFIG_X86_PAE (and CONFIG_HIGHMEM64G - > possibly needed, which is what the kernel config file for Fedora Core > 11 has): >

Re: inode block address

2009-03-10 Thread Peter Teoh
The proper term to use is inode number, block number (or block ID), or inode structure. As far as possible, for both of these information, it is NOT saved in the storage space. reason is because it is supposed to be calculated. For example - from kernel source fs/ext2/inode.c: static struct ex

Re: inode block address

2009-03-10 Thread Sandeep K Sinha
On Tue, Mar 10, 2009 at 2:18 PM, Manish Katiyar wrote: > On Tue, Mar 10, 2009 at 1:06 PM, Sagar lokhande > wrote: >> hi all >> how can i find  the inode block address? > or do you mean "inode bitmap block" ? > [ccing kernelnewbies] > > What do you mean by that ? Do you mean the block numbers

Re: load/store uops

2009-03-10 Thread Shinu
> > > Is this based on a specific problem you're experiencing ? > For example, the RMW could not be atomic, resulting in corruption of some > reg(s), > > > I am trying to add PEBS support to OPrfoile .The metrics for front_end event are load_retired and store_retired. I want to know what is the sig

Re: inode block address

2009-03-10 Thread Manish Katiyar
On Tue, Mar 10, 2009 at 1:06 PM, Sagar lokhande wrote: > hi all > how can i find  the inode block address? [ccing kernelnewbies] What do you mean by that ? Do you mean the block numbers for a particular inode ?? Thanks - Manish > -- > To unsubscribe from this list: send the line "unsubscribe l

Re: any NX memory areas?

2009-03-10 Thread Peter Teoh
Sorry, my mistake, PAE is required yes, and then 32bit Linux Kernel will have NX enabled: PAE can be enabled with CONFIG_X86_PAE (and CONFIG_HIGHMEM64G - possibly needed, which is what the kernel config file for Fedora Core 11 has): In arch/x86/mm/init_32.c: #ifdef CONFIG_X86_PAE set_nx(

Re: Include path for module compilation

2009-03-10 Thread Vishal Thanki
yea.. its defined as "extern" there.. and no, don't include ".c" file :) i believe that ur kernel is not built with timekeeping.o.. can you send me the output of "cat /proc/kallsyms | grep xtime" command ?? vishal Harsha wrote: On Mon, Mar 9, 2009 at 11:29 PM, Vishal Thanki wrote: its dec

Re: Include path for module compilation

2009-03-10 Thread Vishal Thanki
its declared in linux/time/timekeeping.c ref : http://lxr.linux.no/linux+v2.6.28.7/kernel/time/timekeeping.c#L45 btw, have you tried by loading the module?? does it complain in loading it??? Harsha wrote: Hi all, After reading the The Linux Kernel Module Programming Guide, I have written a v