Linux Kernel Newbies

• Thread Index

• Re: Driver initializaton order
  • From: Greg KH <greg@xxxxxxxxx>
• Driver initializaton order
  • From: devzero@xxxxxx
• Re: Compilation issue with spin_lock_bh
  • From: Sanjay Acharya <sacharya@xxxxxxxxxxxxx>
• Re: Compilation issue with spin_lock_bh
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Compilation issue with spin_lock_bh
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Compilation issue with spin_lock_bh
  • From: Sanjay Acharya <sacharya@xxxxxxxxxxxxx>
• Re: Compilation issue with spin_lock_bh
  • From: Sanjay Acharya <sacharya@xxxxxxxxxxxxx>
• Re: getchar issue
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Compilation issue with spin_lock_bh
  • From: Josef Sipek <jsipek@xxxxxxxxxxxxxxxxx>
• Re: Nothing printed from custom /proc/foo
  • From: Tyler <tyler@xxxxxxxx>
• Re: Compilation issue with spin_lock_bh
  • From: Sanjay Acharya <sacharya@xxxxxxxxxxxxx>
• Kernel Socket APIs
  • From: Talib Alium <talibalm@xxxxxxxxxxx>
• getchar issue
  • From: Soumya Kanta Panigrahi <soumya.panigrahi@xxxxxxxxx>
• Nothing printed from custom /proc/foo
  • From: "JP Beaudry" <jp_beaudry@xxxxxxxxxxx>
• Re: simulation of processes competing?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: unexpected PLT reloc type 0x00
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: while(1) in init_module()
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: /proc/interrupts
  • From: Nauman Tahir <nauman.tahir@xxxxxxxxx>
• Re: detect keypress
  • From: Daniel Glazman <daniel@xxxxxxxxxxx>
• Re: detect keypress
  • From: Jan Hudec <bulb@xxxxxx>
• detect keypress
  • From: jerome lacoste <jerome.lacoste@xxxxxxxxx>
• Re: local_irq_disable()
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: signal pending confusion !!!
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• RE: /proc/interrupts
  • From: akumar@xxxxxxxxxxxxxxxxxx
• RE: /proc/interrupts
  • From: akumar@xxxxxxxxxxxxxxxxxx
• Re: local_irq_disable()
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• /proc/interrupts
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: local_irq_disable()
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: Compilation issue with spin_lock_bh
  • From: Josef Sipek <jsipek@xxxxxxxxxxxxxxxxx>
• Compilation issue with spin_lock_bh
  • From: Sanjay Acharya <sacharya@xxxxxxxxxxxxx>
• signal pending confusion !!!
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: source codes for library functions and for commands
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: local_irq_disable()
  • From: Vijay Subramanian <subramanian.vijay@xxxxxxxxx>
• Re: local_irq_disable()
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: dummy fs
  • From: Greg KH <greg@xxxxxxxxx>
• RE: Passing user-space addr. to PCI driver?
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: Passing user-space addr. to PCI driver?
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: Passing user-space addr. to PCI driver?
  • From: Tyler <tyler@xxxxxxxx>
• RE: Passing user-space addr. to PCI driver?
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• Re: local_irq_disable()
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: dummy fs
  • From: Tyler <tyler@xxxxxxxx>
• Re: simulation of processes competing?
  • From: Tyler <tyler@xxxxxxxx>
• Re: SIGUSR1 function call?
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: local_irq_disable()
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: Query regarding dual boot?
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: simulation of processes competing?
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: SIGUSR1 function call?
  • From: Sergey Semenov <sergey.semionov@xxxxxxxxx>
• Re: local_irq_disable()
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: SIGUSR1 function call?
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: SIGUSR1 function call?
  • From: Sergey Semenov <sergey.semionov@xxxxxxxxx>
• Re: Information regarding ELF
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: SIGUSR1 function call?
  • From: Sergey Semenov <sergey.semionov@xxxxxxxxx>
• Re: namespace issue...with types u32 etc
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Query regarding dual boot?
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• simulation of processes competing?
  • From: Yang Huang <justin8086@xxxxxxxxx>
• Re: Information regarding ELF
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Information regarding ELF
  • From: Soumya Kanta Panigrahi <soumya.panigrahi@xxxxxxxxx>
• namespace issue...with types u32 etc
  • From: charan raj <c.charan@xxxxxxxxx>
• Re: Query regarding dual boot?
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: local_irq_disable()
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Query regarding dual boot?
  • From: Badari Prasad <h.badari@xxxxxxxxx>
• Re: local_irq_disable()
  • From: Anupam Kapoor <anupam.kapoor@xxxxxxxxx>
• Re: local_irq_disable()
  • From: Nauman Tahir <nauman.tahir@xxxxxxxxx>
• Re: A Question about the interrupt 13
  • From: Anupam Kapoor <anupam.kapoor@xxxxxxxxx>
• Re: local_irq_disable()
  • From: Anupam Kapoor <anupam.kapoor@xxxxxxxxx>
• Re: Query regarding dual boot?
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Query regarding dual boot?
  • From: Badari Prasad <h.badari@xxxxxxxxx>
• Re: Passing user-space addr. to PCI driver?
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Passing user-space addr. to PCI driver?
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• Re: "struct pci_dev" allocation?
  • From: Greg KH <greg@xxxxxxxxx>
• "struct pci_dev" allocation?
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• dummy fs
  • From: Jan Koss <kossjan@xxxxxxxxx>
• Re: Problem in reading device file
  • From: Ivan Korzakow <ivan.korzakow@xxxxxxxxx>
• Re: local_irq_disable()
  • From: Nauman Tahir <nauman.tahir@xxxxxxxxx>
• Re: local_irq_disable()
  • From: Gaurav Dhiman <gaurav4lkg@xxxxxxxxx>
• Re: A Question about the interrupt 13
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: regarding kernel version 2.6.9
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• A Question about the interrupt 13
  • From: dn79@xxxxxxx
• Re: while(1) in init_module()
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• local_irq_disable()
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: source codes for library functions and for commands
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: regarding kernel version 2.6.9
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• regarding kernel version 2.6.9
  • From: hari krishna <kernel2006hari@xxxxxxxxxxxxxx>
• unexpected PLT reloc type 0x00
  • From: Anup M <anupm@xxxxxxxxx>
• Re: source codes for library functions and for commands
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: while(1) in init_module()
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• source codes for library functions and for commands
  • From: Badari Prasad <h.badari@xxxxxxxxx>
• Re: PCI device init?
  • From: Greg KH <greg@xxxxxxxxx>
• PCI device init?
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• Problem in reading device file
  • From: kanishk rastogi <kanishk_rastogi85@xxxxxxxxx>
• RE: Problem in Reading the Device file
  • From: "Bennett, Robert P" <Robert.Bennett@xxxxxx>
• makefile for 2.6 kernel
  • From: anil dahiya <ak_ait@xxxxxxxxx>
• Re: makefile for 2.6 kernel
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: Problem in Reading the Device file
  • From: kanishk rastogi <kanishk_rastogi85@xxxxxxxxx>
• Re: SIGUSR1 function call?
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: regarding PCI , cPCI, PMC
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Basic PCI driver questions
  • From: Greg KH <greg@xxxxxxxxx>
• Re: compile a kernel module statically into kernel ?
  • From: Roland Kletzing <devzero@xxxxxx>
• Re: Spinlock debugging
  • From: Sanjay Acharya <sacharya@xxxxxxxxxxxxx>
• Re: Problem in Reading the Device file
  • From: Greg KH <greg@xxxxxxxxx>
• Re: while(1) in init_module()
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• regarding PCI , cPCI, PMC
  • From: hari krishna <kernel2006hari@xxxxxxxxxxxxxx>
• SIGUSR1 function call?
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• Re: Spinlock debugging
  • From: "RamaRao" <kramarao@xxxxxxxxxx>
• Problem in Reading the Device file
  • From: kanishk rastogi <kanishk_rastogi85@xxxxxxxxx>
• Re: Spinlock debugging
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Spinlock debugging
  • From: Bahadir Balban <bilgehan.balban@xxxxxxxxx>
• Spinlock debugging
  • From: Bahadir Balban <bahadir.balban@xxxxxxxxx>
• Re: while(1) in init_module()
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: while(1) in init_module()
  • From: Nauman Tahir <nauman.tahir@xxxxxxxxx>
• regarding GUI for Hrdware cards like ARINC429
  • From: hari krishna <kernel2006hari@xxxxxxxxxxxxxx>
• while(1) in init_module()
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: UML in 2.6 kernel mainline works?
  • From: Nauman Tahir <nauman.tahir@xxxxxxxxx>
• Re: How to check the history of system load?
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: How to check the history of system load?
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: How to check the history of system load?
  • From: sanjay kumar <xs2sanjay@xxxxxxxxx>
• Re: How to check the history of system load?
  • From: Yang Huang <justin8086@xxxxxxxxx>
• Re: How to check the history of system load?
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• How to check the history of system load?
  • From: Yang Huang <justin8086@xxxxxxxxx>
• Urgent help required
  • From: Hari Prashanth <hari.prashanth@xxxxxxxxxxx>
• Re: Devices, IRQs and handlers
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: Devices, IRQs and handlers
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Devices, IRQs and handlers
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Need help: hook for executing task
  • From: Claudio Scordino <cloud.of.andor@xxxxxxxxx>
• Re: Devices, IRQs and handlers
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: Devices, IRQs and handlers
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Devices, IRQs and handlers
  • From: Sven Schuster <schuster.sven@xxxxxx>
• Re: Devices, IRQs and handlers
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Devices, IRQs and handlers
  • From: Vijay Subramanian <subramanian.vijay@xxxxxxxxx>
• Re: UML in 2.6 kernel mainline works?
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Devices, IRQs and handlers
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: PCI driver confusion
  • From: Bhanu Kalyan Chetlapalli <chbhanukalyan@xxxxxxxxx>
• Re: kernel control path and interrupts
  • From: Bhanu Kalyan Chetlapalli <chbhanukalyan@xxxxxxxxx>
• Re: UML in 2.6 kernel mainline works?
  • From: Josef Sipek <jsipek@xxxxxxxxxxxxxxxxx>
• UML in 2.6 kernel mainline works?
  • From: Bhanu Kalyan Chetlapalli <chbhanukalyan@xxxxxxxxx>
• kernel control path and interrupts
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: Devices, IRQs and handlers
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Devices, IRQs and handlers
  • From: Vijay Subramanian <subramanian.vijay@xxxxxxxxx>
• Re: Re: kprobes & task_struct
  • From: Frank Beckmann <rootman@xxxxxx>
• Devices, IRQs and handlers
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: Data not reflected in case of multipage bio
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxxx>
• Re: compile a kernel module statically into kernel ?
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: priorities to signal
  • From: Vijay Subramanian <subramanian.vijay@xxxxxxxxx>
• priorities to signal
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: Stackable File system
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: MMUless Linux 2.6 for x86
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: compile a kernel module statically into kernel ?
  • From: Greg KH <greg@xxxxxxxxx>
• compile a kernel module statically into kernel ?
  • From: devzero@xxxxxx
• Re: Stackable File system
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: MMUless Linux 2.6 for x86
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: About generic_file_read()
  • From: prasad Musale <prasad.musale@xxxxxxxxx>
• MMUless Linux 2.6 for x86
  • From: +BigNose <bignose@xxxxxxxxxx>
• Re: Stackable File system
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: Stackable File system
  • From: prasad Musale <prasad.musale@xxxxxxxxx>
• Re: Stackable File system
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Stackable File system
  • From: prasad Musale <prasad.musale@xxxxxxxxx>
• Basic PCI driver questions
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• Re: seperation of decompression from bootstrap in linux kernel
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: About generic_file_read()
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: About generic_file_read()
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• About generic_file_read()
  • From: prasad Musale <prasad.musale@xxxxxxxxx>
• PCI driver confusion
  • From: Medeiros Edward M NPRI <MedeirosEM@xxxxxxxxxxxxxxxxx>
• Re: makefile for 2.6 kernel
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• seperation of decompression from bootstrap in linux kernel
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: generic_file_read()
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: generic_file_read()
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: generic_file_read()
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: makefile for 2.6 kernel
  • From: Nauman Tahir <nauman.tahir@xxxxxxxxx>
• Re: generic_file_read()
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: generic_file_read()
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Re: Regarding Page alignment
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• generic_file_read()
  • From: Dhaval Shirsath <dhavalrs@xxxxxxxxx>
• Re: Unlikely and likely() functions....
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: Doubt regarding PCI access in ixp425 arch
  • From: srikanth <sri@xxxxxxxxxxxxxxxxxx>
• Re: Regarding Page alignment
  • From: Sanjay Acharya <sacharya@xxxxxxxxxxxxx>
• Re: Regarding Page alignment
  • From: eliad lubovsky <eliad.lubovsky@xxxxxxxxx>
• regarding API's for ethernet type driver
  • From: hari krishna <kernel2006hari@xxxxxxxxxxxxxx>
• RE: Regarding Page alignment
  • From: "Kirk True" <ktrue@xxxxxxxxxxx>
• Regarding Page alignment
  • From: Sanjay Acharya <sacharya@xxxxxxxxxxxxx>
• Re: call_usermodehelper dont't execute mysql client?
  • From: toni <agar9938@xxxxxxxxxxxxxxxxxx>
• Doubt regarding PCI access in ixp425 arch
  • From: srikanth <sri@xxxxxxxxxxxxxxxxxx>
• Doubt regarding PCI access in ixp425 arch
  • From: srikanth <sri@xxxxxxxxxxxxxxxxxx>
• Re: call_usermodehelper dont't execute mysql client?
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Unlikely and likely() functions....
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: Unlikely and likely() functions....
  • From: Anupam Kapoor <anupam.kapoor@xxxxxxxxx>
• Unlikely and likely() functions....
  • From: charan raj <c.charan@xxxxxxxxx>
• makefile for 2.6 kernel
  • From: anil dahiya <ak_ait@xxxxxxxxx>
• Re: PCI Device Drivers
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: makefile for 2.6 kernel
  • From: Sam Ravnborg <sam@xxxxxxxxxxxx>
• Re: PCI Device Drivers
  • From: Sonja Tideman <sonjat@xxxxxxxxx>
• Re: PCI Device Drivers
  • From: Greg KH <greg@xxxxxxxxx>
• PCI Device Drivers
  • From: Sonja Tideman <sonjat@xxxxxxxxx>
• Re: about default_ldt
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Thread Scheduling - Does NPTL support PTHREAD_SCOPE_PROCESS ?
  • From: Learner <ruxyz@xxxxxxxxx>
• call_usermodehelper dont't execute mysql client?
  • From: toni <agar9938@xxxxxxxxxxxxxxxxxx>
• Re: Data not reflected in case of multipage bio
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Data not reflected in case of multipage bio
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxxxx>
• Re: pci_find_device removal
  • From: Greg KH <greg@xxxxxxxxx>
• Re: pci_find_device removal
  • From: Sanjay Acharya <sacharya@xxxxxxxxxxxxx>
• Re: pci_find_device removal
  • From: Greg KH <greg@xxxxxxxxx>
• pci_find_device removal
  • From: Sanjay Acharya <sacharya@xxxxxxxxxxxxx>
• Re: USB device query
  • From: Greg KH <greg@xxxxxxxxx>
• Re: putting sysfs on a diet
  • From: Greg KH <greg@xxxxxxxxx>
• Why tcp_collapse()? Unnecessary copying of data??
  • From: Tomas Telensky <tomas@xxxxxxxxx>
• regarding allocb
  • From: "kishore" <kishore@xxxxxxxxxxxxxxxxxxx>
• RE: How to send signals from kernel space to user space.
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• about default_ldt
  • From: orca chen <orca.chen@xxxxxxxxx>
• putting sysfs on a diet
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: USB device query
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: what is a wrapper function?
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: what is a wrapper function?
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: what is a wrapper function?
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: what is a wrapper function?
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• what is a wrapper function?
  • From: "Md.Zaheeruddin Khan" <zaheer031@xxxxxxxxx>
• USB device query
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: Re: kprobes & task_struct
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: __bread freezes for physical device.
  • From: Abhishek Gupta <abhishekgupt@xxxxxxxxx>
• Re: documentation
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: kprobes & task_struct
  • From: Frank Beckmann <rootman@xxxxxx>
• Re: Re: Changing the state of a process
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Re: Changing the state of a process
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxx>
• Re: Re: Changing the state of a process
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Re: Changing the state of a process
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxx>
• Re: Re: Changing the state of a process
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Get the full path of the current process?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: hai
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: hai
  • From: Tetsuo Handa <from-kernelnewbies@xxxxxxxxxxxxxxxxxxx>
• Re: hai
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• hai
  • From: "kishore" <kishore@xxxxxxxxxxxxxxxxxxx>
• Re: Get the full path of the current process?
  • From: Tetsuo Handa <from-kernelnewbies@xxxxxxxxxxxxxxxxxxx>
• Re: Get the full path of the current process?
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Get the full path of the current process?
  • From: NAHieu <nahieu@xxxxxxxxx>
• Why doesn't my system have the core_setuid_ok key?
  • From: jared <demottjar@xxxxxxxxx>
• Re: how to use errno in kernel loadable modules
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: how to use errno in kernel loadable modules
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: how to use errno in kernel loadable modules
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: how to use errno in kernel loadable modules
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Re: Changing the state of a process
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: how to use errno in kernel loadable modules
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: how to use errno in kernel loadable modules
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: how to use errno in kernel loadable modules
  • From: Tetsuo Handa <from-kernelnewbies@xxxxxxxxxxxxxxxxxxx>
• Re: Re: Changing the state of a process
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Interrupts & IDT on i386
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: how to use errno in kernel loadable modules
  • From: "kishore" <kishore@xxxxxxxxxxxxxxxxxxx>
• always update file mode when updating file content?
  • From: NAHieu <nahieu@xxxxxxxxx>
• Re: how to use errno in kernel loadable modules
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: Re: Re: Changing the state of a process
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Interrupts & IDT on i386
  • From: Bhanu Kalyan Chetlapalli <chbhanukalyan@xxxxxxxxx>
• Re: Interrupts & IDT on i386
  • From: Bhanu Kalyan Chetlapalli <chbhanukalyan@xxxxxxxxx>
• Re: how to use errno in kernel loadable modules
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: how to use errno in kernel loadable modules
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: how to use errno in kernel loadable modules
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: how to build .ko on linux
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: Help: Remote debugging using gdb
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: unresolved symbols proc_register and proc_unregister
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• how to use errno in kernel loadable modules
  • From: "kishore" <kishore@xxxxxxxxxxxxxxxxxxx>
• Re: __bread freezes for physical device.
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: Re: Changing the state of a process
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Help: Remote debugging using gdb
  • From: zubair khalil <mzubairkhalil@xxxxxxxxxxx>
• Re: unresolved symbols proc_register and proc_unregister
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: unresolved symbols proc_register and proc_unregister
  • From: Tetsuo Handa <from-kernelnewbies@xxxxxxxxxxxxxxxxxxx>
• Re: Re: Changing the state of a process
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: kprobes & task_struct
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• unresolved symbols proc_register and proc_unregister
  • From: "kishore" <kishore@xxxxxxxxxxxxxxxxxxx>
• __bread freezes for physical device.
  • From: Abhishek Gupta <abhishekgupt@xxxxxxxxx>
• Re: newbie---Regarding to write the device drivers for Full Duplex Ethernet Card in RT Linux
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: Re: Changing the state of a process
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: newbie---Regarding to write the device drivers for Full Duplex Ethernet Card in RT Linux
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: documentation
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• documentation
  • From: "Ms Jimena N." <phenomenes@xxxxxxxxx>
• __bread freezes for physical device.
  • From: Abhishek Gupta <abhishekgupt@xxxxxxxxx>
• kprobes & task_struct
  • From: Frank Beckmann <rootman@xxxxxx>
• Re: Interrupts & IDT on i386
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: newbie---Regarding to write the device drivers for Full Duplex Ethernet Card in RT Linux
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Interrupts & IDT on i386
  • From: Bhanu Kalyan Chetlapalli <chbhanukalyan@xxxxxxxxx>
• newbie---Regarding to write the device drivers for Full Duplex Ethernet Card in RT Linux
  • From: hari krishna <kernel2006hari@xxxxxxxxxxxxxx>
• Re: Panic while booting a recompiled kernel
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Panic while booting a recompiled kernel
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: how to build .ko on linux
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Panic while booting a recompiled kernel
  • From: Tetsuo Handa <from-kernelnewbies@xxxxxxxxxxxxxxxxxxx>
• Re: how to build .ko on linux
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• how to build .ko on linux
  • From: "kishore" <kishore@xxxxxxxxxxxxxxxxxxx>
• Re: Panic while booting a recompiled kernel
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: Panic while booting a recompiled kernel
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Panic while booting a recompiled kernel
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: Changing the state of a process
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• RE: proc_fs.o: unresolved symbol proc_register
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• Re: Fwd: Problem in inserting a simple module in kernel 2.6.5
  • From: hiran <hiran_ramankutty@xxxxxxxxxxxxxx>
• Re: proc_fs.o: unresolved symbol proc_register
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: Problem in inserting a simple module in kernel 2.6.5
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: Changing the state of a process
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Problem in inserting a simple module in kernel 2.6.5
  • From: Badari Prasad <h.badari@xxxxxxxxx>
• Re: need help : User mode linux
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: why sys_mmap2 not use struct mmap_arg_struct
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Problem in inserting a simple module in kernel 2.6.5
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Problem in inserting a simple module in kernel 2.6.5
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Fwd: Problem in inserting a simple module in kernel 2.6.5
  • From: Badari Prasad <h.badari@xxxxxxxxx>
• Re: Problem in inserting a simple module in kernel 2.6.5
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• proc_fs.o: unresolved symbol proc_register
  • From: "kishore" <kishore@xxxxxxxxxxxxxxxxxxx>
• Problem in inserting a simple module in kernel 2.6.5
  • From: Badari Prasad <h.badari@xxxxxxxxx>
• page refcounts?
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: need help : User mode linux
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Kernel 2.6 on x86_32 with more than 4GB ram ?
  • From: "Malkocoglu" <zartzurter@xxxxxxxxx>
• Re: Changing the state of a process
  • From: Jan Hudec <bulb@xxxxxx>
• need help : User mode linux
  • From: hari krishnan <p.harikrishnan22@xxxxxxxxx>
• Re: Open files not shared with the child process ?
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: Open files not shared with the child process ?
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: Changing the state of a process
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: Kernel 2.6 on x86_32 with more than 4GB ram ?
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: Kernel 2.6 on x86_32 with more than 4GB ram ?
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• [Query] regarding sock_ioctl in linux kernel
  • From: Satinder <jeet_sat12@xxxxxxxxxxx>
• Kernel 2.6 on x86_32 with more than 4GB ram ?
  • From: "Malkocoglu" <zartzurter@xxxxxxxxx>
• Re: module code coverage
  • From: Adil Mujeeb <mujeeb.adil@xxxxxxxxx>
• Re: module code coverage
  • From: Greg KH <greg@xxxxxxxxx>
• Re: module code coverage
  • From: Adil Mujeeb <mujeeb.adil@xxxxxxxxx>
• Re: module code coverage
  • From: Greg KH <greg@xxxxxxxxx>
• Re: How to create node in /dev
  • From: Greg KH <greg@xxxxxxxxx>
• RE: How to create node in /dev
  • From: "Nori, Soma Sekhar" <nsekhar@xxxxxx>
• how to increase the signal queue size..
  • From: ppunnam@xxxxxxxxxxx
• How to create node in /dev
  • From: "Martin Mancuska" <borgcube@xxxxxxxxxx>
• Another site for kernel patch
  • From: Giovanni Roggio <gio72002@xxxxxxxx>
• Re: Open files not shared with the child process ?
  • From: Florin Malita <fmalita@xxxxxxxxx>
• Re: Open files not shared with the child process ?
  • From: Jan Hudec <bulb@xxxxxx>
• why sys_mmap2 not use struct mmap_arg_struct
  • From: Bao Zhao <baozhaolinuxer@xxxxxxxxx>
• Re: Open files not shared with the child process ?
  • From: George Zhim <georgezhim@xxxxxxxxx>
• Re: Open files not shared with the child process ?
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: Open files not shared with the child process ?
  • From: Jan Hudec <bulb@xxxxxx>
• module code coverage
  • From: Adil Mujeeb <mujeeb.adil@xxxxxxxxx>
• Re: Changing the state of a process
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Open files not shared with the child process ?
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Open files not shared with the child process ?
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: Changing the state of a process
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Sending 5 consecutive keyboard LED on's.
  • From: Andrew Chuah <hachuah@xxxxxxxxx>
• Re: Error in inserting module
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: Error in inserting module
  • From: prasad Musale <prasad.musale@xxxxxxxxx>
• Re: Changing the state of a process
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Error in inserting module
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: Red-Black tree structure in Kernel
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Red-Black tree structure in Kernel
  • From: ST <steamboattt@xxxxxxxxx>
• Re: How to send signals from kernel space to user space.
  • From: ST <steamboattt@xxxxxxxxx>
• Re: Error in inserting module
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: Red-Black tree structure in Kernel
  • From: fjmartinez@xxxxxxxxxx
• Re: Error in inserting module
  • From: "K.R. Foley" <kr@xxxxxxxxxx>
• Re: Error in inserting module
  • From: prasad Musale <prasad.musale@xxxxxxxxx>
• Re: zImage code and position independence
  • From: "Malkocoglu" <zartzurter@xxxxxxxxx>
• Re: How to send signals from kernel space to user space.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [RFC] TOMOYO Linux released!
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: How to send signals from kernel space to user space.
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: How to send signals from kernel space to user space.
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• How to send signals from kernel space to user space.
  • From: "Narendra V Kulkarni" <narendra@xxxxxxxxxxx>
• Re: problem in do_tcp_sendpages
  • From: Jamie Lokier <jamie@xxxxxxxxxxxxx>
• Basic question on arch/i386
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Changing the state of a process
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: problem in do_tcp_sendpages
  • From: "David S. Miller" <davem@xxxxxxxxxxxxx>
• Re: problem in do_tcp_sendpages
  • From: "David S. Miller" <davem@xxxxxxxxxxxxx>
• Re: problem in do_tcp_sendpages
  • From: Jamie Lokier <jamie@xxxxxxxxxxxxx>
• Re: problem in do_tcp_sendpages
  • From: "David S. Miller" <davem@xxxxxxxxxxxxx>
• Re: [RFC] TOMOYO Linux released!
  • From: Tetsuo Handa <from-kernelnewbies@xxxxxxxxxxxxxxxxxxx>
• Re: Query about sock_release
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: Error in inserting module
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Red-Black tree structure in Kernel
  • From: Maziar H <steamboattt@xxxxxxxxx>
• Re: [RFC] TOMOYO Linux released!
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: problem in do_tcp_sendpages
  • From: Jamie Lokier <jamie@xxxxxxxxxxxxx>
• Re: Error in inserting module
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• ttyy_old_pgrp doubt
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• IPI doubt
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• tty_old_pgrp doubt
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Error in inserting module
  • From: prasad Musale <prasad.musale@xxxxxxxxx>
• Re: error in /usr/src/linux/scripts/basic/fixdep.c
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: QUERY regarding semaphores?
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Query about sock_release
  • From: Satinder <jeet_sat12@xxxxxxxxxxx>
• Re: Dereferencing a null pointer in a module
  • From: Hendrik Post <hendrik@xxxxxxxxxxxx>
• Re: Dereferencing a null pointer in a module
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: Dereferencing a null pointer in a module
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• R: Dereferencing a null pointer in a module
  • From: "Perego Paolo Franco" <p.perego@xxxxxxxx>
• Dereferencing a null pointer in a module
  • From: Hendrik Post <hendrik@xxxxxxxxxxxx>
• Re: problem in do_tcp_sendpages
  • From: "David S. Miller" <davem@xxxxxxxxxxxxx>
• Re: problem in do_tcp_sendpages
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: problem in do_tcp_sendpages
  • From: Sanjay Kumar <coolsanjay@xxxxxxxxx>
• Re: problem in do_tcp_sendpages
  • From: "David S. Miller" <davem@xxxxxxxxxxxxx>
• Re: Re: daemonize and allow_signal (was: Re: Re: Re: kernel thread blocked in sock_recvmsg() not kill-able)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• QUERY regarding semaphores?
  • From: Badari Prasad <h.badari@xxxxxxxxx>
• problem in do_tcp_sendpages
  • From: Sanjay Kumar <coolsanjay@xxxxxxxxx>
• Re: how to make linux program to demon
  • From: Badari Prasad <h.badari@xxxxxxxxx>
• RE: how to make linux program to demon
  • From: "Perego Paolo Franco" <p.perego@xxxxxxxx>
• Re: how to make linux program to demon
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: how to make linux program to demon
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• how to make linux program to demon
  • From: ppunnam@xxxxxxxxxxx
• Re: QUERY regarding semaphores?
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: daemonize and allow_signal (was: Re: Re: Re: kernel thread blocked in sock_recvmsg() not kill-able)
  • From: toni <agar9938@xxxxxxxxxxxxxxxxxx>
• Re: QUERY regarding semaphores?
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: QUERY regarding semaphores?
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: QUERY regarding semaphores?
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: userspace USB drivers
  • From: "Wed, 21 Dec 2005 15:45:10 +0100" <diegocalleja@xxxxxxxxx>
• Re: [RFC] TOMOYO Linux released!
  • From: Tetsuo Handa <from-kernelnewbies@xxxxxxxxxxxxxxxxxxx>
• userspace USB drivers
  • From: Bahadir Balban <bilgehan.balban@xxxxxxxxx>
• QUERY regarding semaphores?
  • From: Badari Prasad <h.badari@xxxxxxxxx>
• Re: Assigning priority to work queues linux 2.6
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: [RFC] TOMOYO Linux released!
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• [RFC] TOMOYO Linux released!
  • From: Tetsuo Handa <from-kernelnewbies@xxxxxxxxxxxxxxxxxxx>
• Re: daemonize and allow_signal (was: Re: Re: Re: kernel thread blocked in sock_recvmsg() not kill-able)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Assigning priority to work queues linux 2.6
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: debugging race condintion using kgdb
  • From: Momchil Velikov <velco@xxxxxxxxx>
• debugging race condintion using kgdb
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Assigning priority to work queues linux 2.6
  • From: Vidya Sankar <mailtogvs@xxxxxxxxx>
• Re: Re: kernel thread blocked in sock_recvmsg() not kill-able
  • From: Jan Hudec <bulb@xxxxxx>
• Re: NF_HOOk
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: NF_HOOk
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• NF_HOOk
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• daemonize and allow_signal (was: Re: Re: Re: kernel thread blocked in sock_recvmsg() not kill-able)
  • From: toni <agar9938@xxxxxxxxxxxxxxxxxx>
• wiki user access
  • From: toni <agar9938@xxxxxxxxxxxxxxxxxx>
• Re: how to make vermagic matches
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: how to make vermagic matches
  • From: Simon Wu <simonwu1@xxxxxxxxx>
• Re: EFAULT in an ioctl (in a kernel module) when calling copy_to_user() - why ??
  • From: John Que <qwejohn@xxxxxxxxx>
• Re: EFAULT in an ioctl (in a kernel module) when calling copy_to_user() - why ??
  • From: John Que <qwejohn@xxxxxxxxx>
• Re: EFAULT in an ioctl (in a kernel module) when calling copy_to_user() - why ??
  • From: Sameer Dhavale <sameer.dhavale@xxxxxxxxx>
• Re: EFAULT in an ioctl (in a kernel module) when calling copy_to_user() - why ??
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: Re: Re: kernel thread blocked in sock_recvmsg() not kill-able
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: EFAULT in an ioctl (in a kernel module) when calling copy_to_user() - why ??
  • From: John Que <qwejohn@xxxxxxxxx>
• Re: EFAULT in an ioctl (in a kernel module) when calling copy_to_user() - why ??
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• EFAULT in an ioctl (in a kernel module) when calling copy_to_user() - why ??
  • From: John Que <qwejohn@xxxxxxxxx>
• Re: Re: kernel thread blocked in sock_recvmsg() not kill-able
  • From: toni <agar9938@xxxxxxxxxxxxxxxxxx>
• Re: Re: kernel thread blocked in sock_recvmsg() not kill-able
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Query regarding devfs
  • From: SITARAM SAKTHINARAYANAN <SITARAMSN@xxxxxxxxxx>
• Query?
  • From: Badari Prasad <h.badari@xxxxxxxxx>
• Serial port access in Kernel Module - Direct to HW or through existing Serial driver?
  • From: James Ausmus <james.ausmus@xxxxxxxxx>
• Re: how to make vermagic matches
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: how to make vermagic matches
  • From: Simon Wu <simonwu1@xxxxxxxxx>
• error in /usr/src/linux/scripts/basic/fixdep.c
  • From: Simon Wu <simonwu1@xxxxxxxxx>
• Re: how to make vermagic matches
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• how to make vermagic matches
  • From: Simon Wu <simonwu1@xxxxxxxxx>
• Re: Re: kernel thread blocked in sock_recvmsg() not kill-able
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Re: kernel thread blocked in sock_recvmsg() not kill-able
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: kernel thread blocked in sock_recvmsg() not kill-able
  • From: topi <topi@xxxxxxxxxxxx>
• Re: kernel thread blocked in sock_recvmsg() not kill-able
  • From: toni <agar9938@xxxxxxxxxxxxxxxxxx>
• Re: kernel thread blocked in sock_recvmsg() not kill-able
  • From: toni <agar9938@xxxxxxxxxxxxxxxxxx>
• Re: __ALIGN vs __ALIGN_STR
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• The best way to start porting kernel to new machine
  • From: Nikolai Daskalov <ndaskalov@xxxxxxxxxxxxx>
• Re: using O_DIRECT to write mmap()'ed IO.
  • From: Michael Honeyfield <mhoneyfield@xxxxxxxxx>
• __ALIGN vs __ALIGN_STR
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: Help: Using cpufreq from kernel level
  • From: Mattia Dongili <malattia@xxxxxxxx>
• Help: Using cpufreq from kernel level
  • From: Claudio Scordino <cloud.of.andor@xxxxxxxxx>
• Re: Help-PCI device driver
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: how to get sources for kernel-compatible modules
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: Re: kernel thread blocked in sock_recvmsg() not kill-able
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: kernel thread blocked in sock_recvmsg() not kill-able
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• how 2 debug a core file in linux
  • From: "Md.Zaheeruddin Khan" <zaheer031@xxxxxxxxx>
• Re: kernel thread blocked in sock_recvmsg() not kill-able
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: cr3 register in thread_struct
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: vmalloc Vs kmalloc
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• vmalloc Vs kmalloc
  • From: Sanjay Acharya <sacharya@xxxxxxxxxxxxx>
• Re: using O_DIRECT to write mmap()'ed IO.
  • From: Michael Honeyfield <mhoneyfield@xxxxxxxxx>
• Re: using O_DIRECT to write mmap()'ed IO.
  • From: Michael Honeyfield <mhoneyfield@xxxxxxxxx>
• cr3 register in thread_struct
  • From: Patrick Kirsch <pk@xxxxxxxxxx>
• Re: Makefile problem
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Makefile problem
  • From: madhan lp <madhan.lp@xxxxxxxxx>
• Re: using O_DIRECT to write mmap()'ed IO.
  • From: Learner <ruxyz@xxxxxxxxx>
• Re: using O_DIRECT to write mmap()'ed IO.
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: enabling spinlock debugging
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: how to get sources for kernel-compatible modules
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• RE: how to get sources for kernel-compatible modules
  • From: "Aggarwal, VikasX" <vikasx.aggarwal@xxxxxxxxx>
• Re: how to get sources for kernel-compatible modules
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: proc sysctl entry
  • From: Adil Mujeeb <mujeeb.adil@xxxxxxxxx>
• using O_DIRECT to write mmap()'ed IO.
  • From: Michael Honeyfield <mhoneyfield@xxxxxxxxx>
• how to get sources for kernel-compatible modules
  • From: "Aggarwal, VikasX" <vikasx.aggarwal@xxxxxxxxx>
• enabling spinlock debugging
  • From: shaw@xxxxxxxxxx
• Kernel timer migration and its effects
  • From: Shaw <shawvrana@xxxxxxxxx>
• Re: udev database file .udev.tdb created as file not as a directory
  • From: Jan Hudec <bulb@xxxxxx>
• kernel thread blocked in sock_recvmsg() not kill-able
  • From: toni <agar9938@xxxxxxxxxxxxxxxxxx>
• enabling spinlock debugging
  • From: Bahadir Balban <bilgehan.balban@xxxxxxxxx>
• Re: Queue task
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Queue task
  • From: Sergey Semenov <sergey.semionov@xxxxxxxxx>
• Re: 64 bit division ..
  • From: Jan Hudec <bulb@xxxxxx>
• dev_add_pack and sock_recvmsg use
  • From: topi <topi@xxxxxxxxxxxx>
• Re: Queue task
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: How to fixed socket buffer
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• How to fixed socket buffer
  • From: Nhan Thanh Le <ltnhan@xxxxxxxxxx>
• Re: udev database file .udev.tdb created as file not as a directory
  • From: Greg KH <greg@xxxxxxxxx>
• udev database file .udev.tdb created as file not as a directory
  • From: Ahmed A <ahmedcali@xxxxxxxxx>
• Re: 64 bit division ..
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: 64 bit division ..
  • From: Jan Hudec <bulb@xxxxxx>
• Queue task
  • From: Sergey Semenov <sergey.semionov@xxxxxxxxx>
• Re: kernel thread
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: about linux kernel thread
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• dev_add_pack and sock_recvmsg use
  • From: toni <agar9938@xxxxxxxxxxxxxxxxxx>
• Re: dev_add_pack and sock_recvmsg use
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: dev_add_pack and sock_recvmsg use
  • From: Parag N(पराग़) <panemade@xxxxxxxxx>
• Re: about linux kernel thread
  • From: Jan Hudec <bulb@xxxxxx>
• Re: kernel thread
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Re: kernel thread
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Re: kernel thread
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: kernel thread
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: kernel thread
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Re: about linux kernel thread
  • From: "MHD.Tayseer Alquoatli" <idoit.ief@xxxxxxxxx>
• Re: kernel thread
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: kernel thread
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Re: proc sysctl entry
  • From: Adil Mujeeb <mujeeb.adil@xxxxxxxxx>
• Re: 64 bit division ..
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• 64 bit division ..
  • From: ppunnam@xxxxxxxxxxx
• Re: kernel thread
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: How to get Ethernet data from Socket buffer.
  • From: Nhan Thanh Le <ltnhan@xxxxxxxxxx>
• kernel thread
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Re: proc sysctl entry
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: proc sysctl entry
  • From: Adil Mujeeb <mujeeb.adil@xxxxxxxxx>
• Re: proc sysctl entry
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• proc sysctl entry
  • From: Adil Mujeeb <mujeeb.adil@xxxxxxxxx>
• Re: schedule() in interrupt handler
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Query About Queue Depth in SCSI
  • From: Learner <ruxyz@xxxxxxxxx>
• Re: about linux kernel thread
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Handling/Hijacking the Interrupt Exception Table
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Using /dev/mem to access memory allocated with kmalloc
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: about linux kernel thread
  • From: Jan Hudec <bulb@xxxxxx>
• Query About Queue Depth in SCSI
  • From: Satinder <jeet_sat12@xxxxxxxxxxx>
• Handling/Hijacking the Interrupt Exception Table
  • From: Vincenzo Mallozzi <vinjunior@xxxxxxxx>
• Re: Using /dev/mem to access memory allocated with kmalloc
  • From: Marek Olszewski <m.olszewski@xxxxxxxxxxx>
• Re: road map of packet
  • From: Hemant Mohapatra <hemant.mohapatra@xxxxxxxxx>
• RE: road map of packet
  • From: "Steve Iribarne" <steve.iribarne@xxxxxxxxxxxxxxxxxxxxx>
• Re: road map of packet
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: road map of packet
  • From: Hemant Mohapatra <hemant.mohapatra@xxxxxxxxx>
• Re: non-preemptive kernel
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: non-preemptive kernel
  • From: Hsieh Steve <stevecfhsieh@xxxxxxxxx>
• Re: road map of packet
  • From: Rajaram Suryanarayanan <rajaram_linux@xxxxxxxxx>
• Re: unloading a module forcefully in linux 2.4.31
  • From: kinGkonGkoli <raju.us@xxxxxxxxx>
• Re: Using /dev/mem to access memory allocated with kmalloc
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: getname() & IS_ERR
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Re: getname() & IS_ERR
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: road map of packet
  • From: Parag N <panemade@xxxxxxxxx>
• Re: road map of packet
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• road map of packet
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Re: Using /dev/mem to access memory allocated with kmalloc
  • From: Marek Olszewski <m.olszewski@xxxxxxxxxxx>
• Re: How to get Ethernet data from Socket buffer.
  • From: Parag N <panemade@xxxxxxxxx>
• Re: registering a usb driver
  • From: Alex Shepard <ashepard@xxxxxxxxxxxxxxxx>
• Using /dev/mem to access memory allocated with kmalloc
  • From: Marek Olszewski <m.olszewski@xxxxxxxxxxx>
• Re: registering a usb driver
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: non-preemptive kernel
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: non-preemptive kernel
  • From: vijay kalkoti <vijayck@xxxxxxxxx>
• non-preemptive kernel
  • From: Hsieh Steve <stevecfhsieh@xxxxxxxxx>
• Re: Doubt Regarding Compiling Kernel for x86_64
  • From: Matthew Percival <matthew@xxxxxxxxx>
• getname() & IS_ERR
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Doubt Regarding Compiling Kernel for x86_64
  • From: "Balaji Rao" <balajirrao@xxxxxxxxx>
• RE: zImage code and position independence
  • From: "Thekkedath Gopakumar-agt026" <gopakumar.t@xxxxxxxxxxxx>
• registering a usb driver
  • From: Alex Shepard <ashepard@xxxxxxxxxxxxxxxx>
• Re: zImage code and position independence
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• RE: Processor descriptor
  • From: "Yagnavarahan" <yagnavarahan@xxxxxxxxx>
• Processor descriptor
  • From: Ashok Sharma <aks6d@xxxxxxxxxxx>
• unloading a module forcefully in linux 2.4.31
  • From: Sabyasachi Pradhan <spradhan@xxxxxxxxxxxxx>
• zImage code and position independence
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• How to get Ethernet data from Socket buffer.
  • From: Nhan Thanh Le <ltnhan@xxxxxxxxxx>
• Re: dev file
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Re: about linux kernel thread
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: about linux kernel thread
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: about linux kernel thread
  • From: Hsieh Steve <stevecfhsieh@xxxxxxxxx>
• Re: about linux kernel thread
  • From: "MHD.Tayseer" <gilmour@xxxxxxxxxxx>
• Re: kernel panic
  • From: Parag N <panemade@xxxxxxxxx>
• kernel panic
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Re: schedule() in interrupt handler
  • From: Parag N <panemade@xxxxxxxxx>
• Re: schedule() in interrupt handler
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Re: hi
  • From: Parag N <panemade@xxxxxxxxx>
• schedule() in interrupt handler
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• hi
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Re: Execution of kernel does not stop at the break point while doing remote debug (using kgdb).
  • From: Vishal Soni <vishal.linux@xxxxxxxxx>
• about linux kernel thread
  • From: Hsieh Steve <stevecfhsieh@xxxxxxxxx>
• dev file
  • From: Hsieh Steve <stevecfhsieh@xxxxxxxxx>
• Re: .h files
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Execution of kernel does not stop at the break point while doing remote debug (using kgdb).
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Execution of kernel does not stop at the break point while doing remote debug (using kgdb).
  • From: Vishal Soni <vishal.linux@xxxxxxxxx>
• Re: wait_event_interruptible vs wait_for_completion_interruptible
  • From: Jan Hudec <bulb@xxxxxx>
• Re: hi
  • From: Parag N <panemade@xxxxxxxxx>
• Re: skb_put() causes the system to loop
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: USB in linux
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• wait_event_interruptible vs wait_for_completion_interruptible
  • From: "T.Krishnanand" <krishnanand.thommandra@xxxxxxxxx>
• Re: USB in linux
  • From: Greg KH <greg@xxxxxxxxx>
• hi
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Re: register_chrdev_region() return value when there is no device file
  • From: Jan Hudec <bulb@xxxxxx>
• register_chrdev_region() return value when there is no device file
  • From: John Que <qwejohn@xxxxxxxxx>
• Re: alsa-driver from kernel 2.4.31
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• USB in linux
  • From: "Nel" <nel14d@xxxxxxxxxxxxxx>
• Finding open count of a particular file
  • From: Learner <ruxyz@xxxxxxxxx>
• alsa-driver from kernel 2.4.31
  • From: "Ravichandran" <sravich@xxxxxxxxxx>
• broken link: patch-page: reiserfs
  • From: "Jean-Stephane Jokeit" <Jean-Stephane.Jokeit@xxxxxxxxxxxxxxxxxx>
• Re: .h files
  • From: Dirk Hünniger <hunniger@xxxxxxxxxxxxxxxxxxxxxx>
• Re: hi
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• Re: .h files
  • From: Greg KH <greg@xxxxxxxxx>
• Re: .h files
  • From: Dirk Hünniger <hunniger@xxxxxxxxxxxxxxxxxxxxxx>
• Re: (New newbie) and (Re: Consulting work needed!) and (.h files)
  • From: Greg KH <greg@xxxxxxxxx>
• (New newbie) and (Re: Consulting work needed!) and (.h files)
  • From: Dirk Hünniger <hunniger@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Consulting work needed!
  • From: Pascal Muller <pascalmuller@xxxxxxxxx>
• Re: Consulting work needed!
  • From: "Keith C Aymar" <keith@xxxxxxxxxxxxxxxxx>
• Re: Consulting work needed!
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Consulting work needed!
  • From: <keith@xxxxxxxxxxxxxxxxx>
• Looking for an I/O performance test tool for iSCSI target
  • From: Manish Verma <mail.manishverma@xxxxxxxxx>
• Re: Help-PCI device driver
  • From: Parag N <panemade@xxxxxxxxx>
• Help-PCI device driver
  • From: SITARAM SAKTHINARAYANAN <SITARAMSN@xxxxxxxxxx>
• Re: how to find pid with cpp ?
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: trying to change compilers
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: stack unwinding in linux 2.4
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Re: stack unwinding in linux 2.4
  • From: Jan Hudec <bulb@xxxxxx>
• Re: hi
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: hi
  • From: Parag N <panemade@xxxxxxxxx>
• Re: KERNEL PANIC FIX SOUGHT
  • From: Parag N <panemade@xxxxxxxxx>
• hi
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Re: Unknown symbol in module
  • From: Parag N <panemade@xxxxxxxxx>
• Re: stack unwinding in linux 2.4
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• Re: how to find pid with cpp ?
  • From: Hemant Mohapatra <hemant.mohapatra@xxxxxxxxx>
• Re: skb_put() causes the system to loop
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• lookup_hash() and lookup_one_len()
  • From: Tetsuo Handa <from-kernelnewbies@xxxxxxxxxxxxxxxxxxx>
• Unknown symbol in module
  • From: Vincenzo Mallozzi <vinjunior@xxxxxxxx>
• Re: trying to change compilers
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: KERNEL PANIC FIX SOUGHT
  • From: Jim Cromie <jim.cromie@xxxxxxxxx>
• Re: use of EXPORT_SYMBOL()
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: KERNEL PANIC FIX SOUGHT
  • From: "Gil Lapidus" <ekoot@xxxxxxxxxxxx>
• Re: KERNEL PANIC FIX SOUGHT
  • From: Jan Hudec <bulb@xxxxxx>
• Re: use of EXPORT_SYMBOL()
  • From: Florin Malita <fmalita@xxxxxxxxx>
• Re: use of EXPORT_SYMBOL()
  • From: Jan Hudec <bulb@xxxxxx>
• Re: stack unwinding in linux 2.4
  • From: Jan Hudec <bulb@xxxxxx>
• Re: KERNEL PANIC FIX SOUGHT
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• KERNEL PANIC FIX SOUGHT
  • From: "kiran kumar" <kiran07_nitk@xxxxxxxxxxxxxx>
• Re: Recursion in process group statistical enumeration
  • From: fjmartinez@xxxxxxxxxx
• Recursion in process group statistical enumeration
  • From: thesp0nge <p.perego@xxxxxxxx>
• Re: kernel version.
  • From: thesp0nge <p.perego@xxxxxxxx>
• Re: how to find pid with cpp ?
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• trying to change compilers
  • From: "Ravichandran" <sravich@xxxxxxxxxx>
• Re: kernel version.
  • From: "Sergey S. Ropchan" <fenix@xxxxxxxxxxx>
• Re: use of EXPORT_SYMBOL()
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• how to find pid with cpp ?
  • From: Mehmet Fatih AKBULUT <mfatihakbulut@xxxxxxxxx>
• Re: use of EXPORT_SYMBOL()
  • From: Sabyasachi Pradhan <spradhan@xxxxxxxxxxxxx>
• Re: use of EXPORT_SYMBOL()
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: use of EXPORT_SYMBOL()
  • From: Sabyasachi Pradhan <spradhan@xxxxxxxxxxxxx>
• Re: use of EXPORT_SYMBOL()
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: virtual interface mac adress
  • From: Rik van Riel <riel@xxxxxxxxxx>
• virtual interface mac adress
  • From: anil dahiya <ak_ait@xxxxxxxxx>
• Re: use of EXPORT_SYMBOL()
  • From: Sabyasachi Pradhan <spradhan@xxxxxxxxxxxxx>
• Re: use of EXPORT_SYMBOL()
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• use of EXPORT_SYMBOL()
  • From: Sabyasachi Pradhan <spradhan@xxxxxxxxxxxxx>
• Re: kernel version.
  • From: Mehmet Fatih AKBULUT <mfatihakbulut@xxxxxxxxx>
• Re: kernel version.
  • From: Nish Aravamudan <nish.aravamudan@xxxxxxxxx>
• Re: kernel version.
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: kernel version.
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: kernel version.
  • From: Jesper Juhl <jesper.juhl@xxxxxxxxx>
• kernel version.
  • From: Mehmet Fatih AKBULUT <mfatihakbulut@xxxxxxxxx>
• skb_put() causes the system to loop
  • From: Samarth <samarth.shetty@xxxxxxxxx>
• kernel panic fix sought
  • From: "Gil Lapidus" <ekoot@xxxxxxxxxxxx>
• Re: "struct pci_bus" related query
  • From: Greg KH <greg@xxxxxxxxx>
• stack unwinding in linux 2.4
  • From: "Saumender Dash" <sdash@xxxxxxxxxxxxxxxxxxx>
• "struct pci_bus" related query
  • From: vidyut karan <kvidyut2000@xxxxxxxxxxx>
• Re: scheduler task queues
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• scheduler task queues
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: Scheduler mod: dropping to low power...
  • From: Matthew Percival <matthew@xxxxxxxxx>
• Re: Doubt in linux/list.h
  • From: Libin Varghese <libinv@xxxxxxxxx>
• Re: Doubt in linux/list.h
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: Doubt in linux/list.h
  • From: Jim Bauer <jfbauer@xxxxxxx>
• Re: Doubt in linux/list.h
  • From: Libin Varghese <libinv@xxxxxxxxx>
• Re: help with RAMDISK: image to big! (35512/8192 blocks)
  • From: William J Beksi <wjbeksi@xxxxxxxxxxx>
• Re: Timing
  • From: Adrian May <adrian@xxxxxxxxxxxxxxxxxxxxxx>
• help with RAMDISK: image to big! (35512/8192 blocks)
  • From: Libin Varghese <libinv@xxxxxxxxx>
• Re: Scheduler mod: dropping to low power...
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• RE: Scheduler mod: dropping to low power...
  • From: 梅 翔 <meixiang_cs93@xxxxxxxxxxx>
• Scheduler mod: dropping to low power...
  • From: Matthew Percival <matthew@xxxxxxxxx>
• Re: Doubt in linux/list.h
  • From: Libin Varghese <libinv@xxxxxxxxx>
• Re: Doubt in linux/list.h
  • From: Jim Bauer <jfbauer@xxxxxxx>
• Re: Fwd: Interrupt
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: Doubt in linux/list.h
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Doubt in linux/list.h
  • From: Libin Varghese <libinv@xxxxxxxxx>
• Fwd: Interrupt
  • From: Roushan Ali <roushan.ali@xxxxxxxxx>
• Re: Interrupt
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Interrupt
  • From: Roushan Ali <roushan.ali@xxxxxxxxx>
• Re: Error while making initrd file
  • From: pradeep singh <2500.pradeep@xxxxxxxxx>
• Re: Error while making initrd file
  • From: Libin Varghese <libinv@xxxxxxxxx>
• Re: objdump of zimage
  • From: Hemant Mohapatra <hemant.mohapatra@xxxxxxxxx>
• objdump of zimage
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: fast communication problem
  • From: Guennadi Liakhovetski <gl@xxxxxxxxx>
• saving file system data structures
  • From: Sabyasachi Pradhan <spradhan@xxxxxxxxxxxxx>
• Re: Timing
  • From: Hayim Shaul <hayim@xxxxxxxxxxxxxx>
• Re: Timing
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Timing
  • From: Adrian May <adrian@xxxxxxxxxxxxxxxxxxxxxx>
• Re: call_usermodehelper's pid ?
  • From: Jan Hudec <bulb@xxxxxx>
• Re: call_usermodehelper's pid ?
  • From: Nhan Thanh Le <ltnhan@xxxxxxxxxx>
• Re: logical/virtual addresses and high-memory
  • From: Rene Herman <rene.herman@xxxxxxxxxxxx>
• Makefile modification from 2.4 to 2.6
  • From: Vincenzo Mallozzi <vinjunior@xxxxxxxx>
• Re: logical/virtual addresses and high-memory
  • From: Bahadir Balban <bilgehan.balban@xxxxxxxxx>
• Re: logical/virtual addresses and high-memory
  • From: George Zhim <georgezhim@xxxxxxxxx>
• Re: logical/virtual addresses and high-memory
  • From: Rene Herman <rene.herman@xxxxxxxxxxxx>
• Re: [PATCH] kernel.h: kill labs(), allow more types in abs()
  • From: Nicolas Kaiser <nikai@xxxxxxxxx>
• Re: logical/virtual addresses and high-memory
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• logical/virtual addresses and high-memory
  • From: Bahadir Balban <bilgehan.balban@xxxxxxxxx>
• PCI and DMA
  • From: Bahadir Balban <bilgehan.balban@xxxxxxxxx>
• Re: Linux TCP/IP Stack Performance Tool
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• call_usermodehelper's pid ?
  • From: George Zhim <georgezhim@xxxxxxxxx>
• [PATCH] kernel.h: kill labs(), allow more types in abs()
  • From: Nicolas Kaiser <nikai@xxxxxxxxx>
• Re: Linux TCP/IP Stack Performance Tool
  • From: Ohad Ben-Cohen <ohadbc@xxxxxxxxx>
• Linux TCP/IP Stack Performance Tool
  • From: Bhanu Kalyan Chetlapalli <chbhanukalyan@xxxxxxxxx>
• Re: microsecond/nanosecond precision in select system call !!
  • From: Nish Aravamudan <nish.aravamudan@xxxxxxxxx>
• Re: Is the nano second resolution in pselect achievable ??
  • From: Nish Aravamudan <nish.aravamudan@xxxxxxxxx>
• Is the nano second resolution in pselect achievable ??
  • From: Indraneel Mukherjee <mukherjee.indraneel@xxxxxxxxx>
• microsecond/nanosecond precision in select system call !!
  • From: Indraneel Mukherjee <mukherjee.indraneel@xxxxxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: "MHD.Tayseer" <gilmour@xxxxxxxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Question about wait queue
  • From: Yang Huang <justin8086@xxxxxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: Jan Hudec <bulb@xxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: "MHD.Tayseer" <gilmour@xxxxxxxxxxx>
• Re: Doubt regarding Interrupt handlers
  • From: Jan Hudec <bulb@xxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Doubt regarding Interrupt handlers
  • From: "Vijay Ram Chitrapu (RCVIJAYD)" <cvijay@xxxxxxxxxxxxxxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: "MHD.Tayseer" <gilmour@xxxxxxxxxxx>
• Re: usb devices listing
  • From: Abdul Razaq <abdulrazaq@xxxxxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: Jan Hudec <bulb@xxxxxx>
• Re: usb devices listing
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Doubt regarding Interrupt handlers
  • From: Jan Hudec <bulb@xxxxxx>
• usb devices listing
  • From: Michel Cunha <michelsouza@xxxxxxxxx>
• Re: How to quickly detect the mode change of a hard disk?
  • From: Hui Cheng <hcheng@xxxxxxxxxxx>
• Broadcast via netlink
  • From: Andreas Gaupmann <andreas.gaupmann@xxxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: Walter Cruz <walter.php@xxxxxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: "MHD.Tayseer" <gilmour@xxxxxxxxxxx>
• net/socket.c
  • From: "Talib Alim" <talibalm@xxxxxxxxxxx>
• irq_vectors.h not found
  • From: Vincenzo Mallozzi <vinjunior@xxxxxxxx>
• Doubt regarding Interrupt handlers
  • From: "Vijay Ram.C" <cvijay@xxxxxxxxxxxxxxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: "MHD.Tayseer" <gilmour@xxxxxxxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: Rajat Jain <rajat.noida.india@xxxxxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Porting to 2.6.14 from 2.4.X
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: How to quickly detect the mode change of a hard disk?
  • From: Pavel Machek <pavel@xxxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: "MHD.Tayseer" <gilmour@xxxxxxxxxxx>
• Porting to 2.6.14 from 2.4.X
  • From: Vincenzo Mallozzi <vinjunior@xxxxxxxx>
• Re: compiling the kernel not using (linux, gcc)
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: reading from /proc/kcore
  • From: Jan Hudec <bulb@xxxxxx>
• compiling the kernel not using (linux, gcc)
  • From: "MHD.Tayseer" <gilmour@xxxxxxxxxxx>
• ANN: wiki updated
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: reading from /proc/kcore
  • From: Sabyasachi Pradhan <spradhan@xxxxxxxxxxxxx>
• Re: reading from /proc/kcore
  • From: Jan Hudec <bulb@xxxxxx>
• Re: System Calls
  • From: Jan Hudec <bulb@xxxxxx>
• Re: How to quickly detect the mode change of a hard disk?
  • From: Hui Cheng <hcheng@xxxxxxxxxxx>
• Re: System Calls
  • From: Surbhi Chitre <csurbhi@xxxxxxxxx>
• Re: System Calls
  • From: Nilesh Agrawal <nilesh.agrawal@xxxxxxxxx>
• Re: System Calls
  • From: Oliver Korpilla <Oliver.Korpilla@xxxxxx>
• System Calls
  • From: "Rajaram Surya" <rajaram_irtt3@xxxxxxxxxxx>
• reading from /proc/kcore
  • From: Sabyasachi Pradhan <spradhan@xxxxxxxxxxxxx>
• Re: A problem with ktimer
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• A problem with ktimer
  • From: Claudio Scordino <cloud.of.andor@xxxxxxxxx>
• Re: How pci_bus_read_config_word is implemented?
  • From: Yang Huang <justin8086@xxxxxxxxx>
• Re: How pci_bus_read_config_word is implemented?
  • From: hiran <hiran_ramankutty@xxxxxxxxxxxxxx>
• Re: How pci_bus_read_config_word is implemented?
  • From: Yang Huang <justin8086@xxxxxxxxx>
• Re: How pci_bus_read_config_word is implemented?
  • From: hiran <hiran_ramankutty@xxxxxxxxxxxxxx>
• How pci_bus_read_config_word is implemented?
  • From: Yang Huang <justin8086@xxxxxxxxx>
• RE:mkinitrd image output problem
  • From: justin <justin8086@xxxxxxxxx>
• mkinitrd image output problem
  • From: nikola@xxxxxxxx (nikola)
• Re: How to quickly detect the mode change of a hard disk?
  • From: "Alejandro Bonilla" <abonilla@xxxxxxxxxxxxxxxxx>
• Re: How to quickly detect the mode change of a hard disk?
  • From: Pavel Machek <pavel@xxxxxxx>
• Re: call_usermodehelper from a timer function ?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: call_usermodehelper from a timer function ?
  • From: Indraneel Mukherjee <mukherjee.indraneel@xxxxxxxxx>
• Re: call_usermodehelper from a timer function ?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• call_usermodehelper from a timer function ?
  • From: Indraneel Mukherjee <mukherjee.indraneel@xxxxxxxxx>
• Re: saving kernel state
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• saving kernel state
  • From: Sabyasachi Pradhan <spradhan@xxxxxxxxxxxxx>
• Re: IP address
  • From: Pranjal Kumar Dutta <pranjalkumardutta@xxxxxxxxx>
• IP address
  • From: Nhan Thanh Le <ltnhan@xxxxxxxxxx>
• Re: what is the function of entry.S?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• New getrusage
  • From: Claudio Scordino <cloud.of.andor@xxxxxxxxx>
• fast communication problem
  • From: Ivan Korzakow <ivan.korzakow@xxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Claudio Scordino <cloud.of.andor@xxxxxxxxx>
• sk_buff real_dev and more questions
  • From: Hayim Shaul <hayim@xxxxxxxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Peter Chubb <peterc@xxxxxxxxxxxxxxxxxx>
• Re: setsockopt() in kernel
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: setsockopt() in kernel
  • From: "JP Beaudry" <jp_beaudry@xxxxxxxxxxx>
• Re: setsockopt() in kernel
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: setsockopt() in kernel
  • From: "JP Beaudry" <jp_beaudry@xxxxxxxxxxx>
• Re: Help - problem connecting to IRC.
  • From: "ajith" <ajithu@xxxxxxxxxx>
• Re: Help - problem connecting to IRC.
  • From: "Rajaram Surya" <rajaram_irtt3@xxxxxxxxxxx>
• Re: Help - problem connecting to IRC.
  • From: Jan Hudec <bulb@xxxxxx>
• Re: Hi ! help !- new to this list
  • From: Jan Hudec <bulb@xxxxxx>
• Help - problem connecting to IRC.
  • From: "Rajaram Surya" <rajaram_irtt3@xxxxxxxxxxx>
• Hi ! help !- new to this list
  • From: "Rajaram Surya" <rajaram_irtt3@xxxxxxxxxxx>
• Re: using ioctl in linux modules
  • From: Jan Hudec <bulb@xxxxxx>
• Ethernet packet size in network drivers
  • From: joey k <joeyk7@xxxxxxxxx>
• Re: what is the function of entry.S?
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: measuring response time of a process
  • From: Filip Iliescu <djpriya@xxxxxxxxx>
• Re: Crashme fails.
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: memory descriptor of threads
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: measuring response time of a process
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Crashme fails.
  • From: "nitin ahuja" <nitin2ahuja@xxxxxxxxxxxxx>
• Re: measuring response time of a process
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: using ioctl in linux modules
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Claudio Scordino <cloud.of.andor@xxxxxxxxx>
• measuring response time of a process
  • From: Filip Iliescu <djpriya@xxxxxxxxx>
• How to quickly detect the mode change of a hard disk?
  • From: Hui Cheng <hcheng@xxxxxxxxxxx>
• making makefile for 2.6 kernel
  • From: anil dahiya <ak_ait@xxxxxxxxx>
• making makefile for 2.6 kernel
  • From: anil dahiya <ak_ait@xxxxxxxxx>
• using ioctl in linux modules
  • From: Hossein Aminaiee <aminaiee@xxxxxxxxx>
• using ioctl in linux modules
  • From: Hossein Aminaiee <aminaiee@xxxxxxxxx>
• what is the function of entry.S?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: setsockopt() in kernel
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Chris Wright <chrisw@xxxxxxxx>
• RE: [PATCH] getrusage sucks
  • From: "Hua Zhong \(hzhong\)" <hzhong@xxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Claudio Scordino <cloud.of.andor@xxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: dean gaudet <dean-list-linux-kernel@xxxxxxxxxx>
• setsockopt() in kernel
  • From: "JP Beaudry" <jp_beaudry@xxxxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Claudio Scordino <cloud.of.andor@xxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Chris Wright <chrisw@xxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Claudio Scordino <cloud.of.andor@xxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: Problem with copy_from_user
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Claudio Scordino <cloud.of.andor@xxxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: "Magnus Naeslund(f)" <mag@xxxxxxxx>
• Re: [PATCH] getrusage sucks
  • From: Claudio Scordino <cloud.of.andor@xxxxxxxxx>
• Re: Problem with copy_from_user
  • From: Jim Bauer <jfbauer@xxxxxxx>
• RE: [PATCH] getrusage sucks
  • From: "Hua Zhong \(hzhong\)" <hzhong@xxxxxxxxx>
• RE: Problem with copy_from_user
  • From: Laurent Nadeau <nadelau@xxxxxxx>
• [PATCH] getrusage sucks
  • From: Claudio Scordino <cloud.of.andor@xxxxxxxxx>
• Re: Problem with copy_from_user
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Re: calculating physical memory address
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>
• Problem with copy_from_user
  • From: Laurent Nadeau <nadelau@xxxxxxx>
• Re: memory descriptor of threads
  • From: Vincenzo Mallozzi <vinjunior@xxxxxxxx>
• Re: Query
  • From: Jan Hudec <bulb@xxxxxx>
• Re: spinlocks and preemption
  • From: Jan Hudec <bulb@xxxxxx>
• Re: calculating physical memory address
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: calculating physical memory address
  • From: pkirsch@xxxxxxxxxx
• Re: memory descriptor of threads
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: memory descriptor of threads
  • From: Vincenzo Mallozzi <vinjunior@xxxxxxxx>
• Re: spinlocks and preemption
  • From: Bahadir Balban <bilgehan.balban@xxxxxxxxx>
• Re: Query
  • From: Fawad Lateef <fawadlateef@xxxxxxxxx>