linux-kernel - Re: Code flow from device connection to device node in /dev creation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHkwNT=U58520GpkNLtBcJVtujh=wN8-+uEXXkFJZSoByvUj7w@mail.gmail.com>
Date:	Sat, 9 Jun 2012 23:57:56 +0530
From:	Anil Nair <anilcoll90@...il.com>
To:	prasannatsmkumar <prasannatsmkumar@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Code flow from device connection to device node in /dev creation

Hi Prasanna,

On Sun, May 27, 2012 at 10:19 AM, prasannatsmkumar
<prasannatsmkumar@...il.com> wrote:

> If I open a device file (say a printer device) who determines the
> correct driver and sends the call? How subsequent calls get processed
> etc. Yes I know the init function will be called while the driver is
> loaded (while running insmod driver.ko). How a open or write call
> comes to the driver from user space? Who keeps track of the driver's
> internal data (*dev) and sends that while calling methods in the
> driver? I am more interested in things like that.

Drivers work in kernel address space. The implementation of the USB in
userspace is through the library libusb, i guess you have visited its
thread in mailing list. You will require a serious reading before
jumping into coding.
Sorry if you have done the required reading. :).

-- 
Regards,
Anil Nair
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/