青青草原综合久久大伊人导航_色综合久久天天综合_日日噜噜夜夜狠狠久久丁香五月_热久久这里只有精品

S.l.e!ep.¢%

像打了激速一樣,以四倍的速度運轉(zhuǎn),開心的工作
簡單、開放、平等的公司文化;尊重個性、自由與個人價值;
posts - 1098, comments - 335, trackbacks - 0, articles - 1
  C++博客 :: 首頁 :: 新隨筆 :: 聯(lián)系 :: 聚合  :: 管理

Writing a device driver for Windows

Posted on 2009-10-30 11:04 S.l.e!ep.¢% 閱讀(597) 評論(1)  編輯 收藏 引用 所屬分類: RootKit

Writing a device driver for Windows

In order to write a device driver for windows, one needs the device driver development kit (ddk) and a c compiler.
According to this article, a device driver's maximum size is 960MB on Windows XP (100MB on NT4, 220MB on Win2K).

Setting up the environment

A proper environment must be setup. Use setenv (which ships with the ddk) to set the environment variables (and what not) to build a driver:
C:\>programme\ntddk\bin\setenv \programme\ntddk.
The argument that is given to setenv must point to the directory under which the ddk is installed.

makefile

The directory that contains the sources for the device driver must have a file called makefile and another file called sources. For a simple device driver, it is sufficient to have one single line in the makefile:
!INCLUDE $(NTMAKEENV)\makefile.def

sources

This file actually contains the names of the files to be compiled:
TARGETNAME=kamel
TARGETPATH=obj
TARGETTYPE=DRIVER

SOURCES=kamel.c writeEvent.c kamelMsg.rc

C_DEFINES=-DUNICODE -DSTRICT
kamel.c is the code for the driver itself, writeEvent.c contains a function that can be called to write messages to the system event log (see below) and kamelMsg.rc contains the strings that are written

Writing the driver

I call the driver we're going to write Kamel. In german, this will then be called Kameltreiber which is a pun german speaking people will understand. So, we're creating (according to the sources file) a file called kamel.c. The first lines contain the includes we need:
#include "ntddk.h"
#include "writeEvent.h"
#include "kamelMsg.h"
ntddk.h must always be included, writeEvent.h contains the declaration of WriteEvent (which is a function to write events, of course) and kamelMsg.h (being created by the message compiler) contains the identifiers of the strings we want to write using WriteEvent.
Each driver needs a DriverEntry function which is called when the driver is loaded:
Now, we use write the forward declarations together with the pragmas alloc_text. They indicate wheather or not the function is pageable.
#define BUFFERSIZE 1024
#define BUFFERTAG  'kmlb'

typedef struct _KAMEL_DRIVER_EXTENSION {
  char buffer[BUFFERSIZE];
} KAMEL_DRIVER_EXTENSION, *PKAMEL_DRIVER_EXTENSION;

KAMEL_DRIVER_EXTENSION* driverExtension=0;


NTSTATUS DriverEntry  (IN PDRIVER_OBJECT DriverObject, IN PUNICODE_STRING RegistryPath);
NTSTATUS CreateCamel  (IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp);
NTSTATUS ReadCamel    (IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp);
NTSTATUS WriteCamel   (IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp);
NTSTATUS ShutdownCamel(IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp);
NTSTATUS CleanupCamel (IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp);
NTSTATUS IoCtlCamel   (IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp);
VOID     CmlUnload    (IN PDRIVER_OBJECT  DriverObject);


#ifdef ALLOC_PRAGMA
#pragma alloc_text(INIT, DriverEntry)
#pragma alloc_text(PAGE, CreateCamel) 
#pragma alloc_text(PAGE, ReadCamel) 
#pragma alloc_text(PAGE, WriteCamel) 
#pragma alloc_text(PAGE, ShutdownCamel)
#pragma alloc_text(PAGE, IoCtlCamel)
#pragma alloc_text(PAGE, CmlUnload)
#endif
NTSTATUS DriverEntry(IN PDRIVER_OBJECT DriverObject, IN PUNICODE_STRING RegistryPath) {

  UNICODE_STRING nameString, linkString;
  PDEVICE_OBJECT deviceObject;
  NTSTATUS status;

  WriteEvent(MSG_DRIVER_ENTRY,DriverObject,NULL);

  RtlInitUnicodeString(&nameString, L"\\Device\\Kamel");

  status = IoCreateDevice(
    DriverObject, 
    sizeof(65533),
    &nameString, 
    0, //FILE_DEVICE_UNKNOWN,
    0, 
    FALSE, 
    &deviceObject);

  if (!NT_SUCCESS(status))
    return status;


  deviceObject->Flags |= DO_DIRECT_IO;
  deviceObject->Flags &= ~DO_DEVICE_INITIALIZING;


  RtlInitUnicodeString(&linkString, L"\\DosDevices\\Kamel");
  status = IoCreateSymbolicLink (&linkString, &nameString);

  if (!NT_SUCCESS(status)) {
    IoDeleteDevice (DriverObject->DeviceObject);
    return status;
  }


  DriverObject->MajorFunction[IRP_MJ_CREATE]         = CreateCamel;
  DriverObject->MajorFunction[IRP_MJ_READ]           = ReadCamel;
  DriverObject->MajorFunction[IRP_MJ_WRITE]          = WriteCamel;
  DriverObject->MajorFunction[IRP_MJ_SHUTDOWN]       = ShutdownCamel;
  DriverObject->MajorFunction[IRP_MJ_DEVICE_CONTROL] = IoCtlCamel;
  
  DriverObject->DriverUnload=CmlUnload;

  // ExAllocatePool is obsolete and ExAllocatePoolWithTag should be used.
  driverExtension = ExAllocatePool(NonPagedPool, sizeof (KAMEL_DRIVER_EXTENSION));

  if(!driverExtension) {
    WriteEvent(MSG_NO_IOALLOCATEDRIVEROBJECTEXTENSION, DriverObject, NULL);
    return STATUS_INSUFFICIENT_RESOURCES;
  }

  RtlZeroMemory(driverExtension->buffer, BUFFERSIZE);

  RtlCopyBytes (driverExtension->buffer, "123456789012345", 16);

  return STATUS_SUCCESS;
}
DriverEntry first writes an Event (using WriteEvent, explained later) so it can be verified that DriverEntry indeed was called. Then, the actual device is created using IoCreateDevice and initialized.

Setting Up Major Functions

An Application communicates with a driver with the driver's Major Functions. These are set in the drivers array of function pointers MajorFunction.

User Visible Name for the driver

In order to create a user-visible name for the device just created, IoCreateSymbolicLink is called.

Allocating Pool Memory

The driver allocates some Pool Memory with ExAllocatePool.
By the way, Paged and Non-Paged Pool Memory sized can be adjusted with the registry keys HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\(Non)PagedPoolSize. The Value specified is the size in bytes.

Programming the Major Functions

In DriverEntry, the Major Functions IRP_MJ_CREATE, IRP_MJ_READ, IRP_MJ_WRITE, IRP_MJ_SHUTDOWN, IRP_MJ_DEVICE_CONTROL were set. Here are the actual functions they point to:

IRP_MJ_CREATE

This function is called when a file using this deivce is created. In Win32Api, Devices are opened using CreateFile which then routes in the function associated with IRP_MJ_CREATE.
NTSTATUS CreateCamel (IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp) {
  WriteEvent(MSG_CREATE,(PVOID)DeviceObject,NULL);

  IoCompleteRequest(Irp,IO_NO_INCREMENT);
  return  STATUS_SUCCESS;
}

IRP_MJ_READ

NTSTATUS ReadCamel(IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp) {
  PUCHAR                      currentAddress;
  PIO_STACK_LOCATION          irpStack;

  WriteEvent(MSG_READ,DeviceObject,NULL);

  if (!driverExtension) {
    WriteEvent(MSG_DRIVEREXTISNULLINREAD,DeviceObject,NULL);
    IoCompleteRequest(Irp, IO_NO_INCREMENT);
    return STATUS_INSUFFICIENT_RESOURCES;
  }
  irpStack = IoGetCurrentIrpStackLocation(Irp);

  if (irpStack->MajorFunction == IRP_MJ_READ) {
    currentAddress = MmGetSystemAddressForMdlSafe(Irp->MdlAddress, NormalPagePriority);

    if (!currentAddress) {
      WriteEvent(MSG_MMGETSYSTEMADDRESS,DeviceObject,NULL);
      IoCompleteRequest(Irp, IO_NO_INCREMENT);
      return STATUS_SUCCESS;
    }
    RtlMoveMemory(currentAddress, 
    driverExtension->buffer+irpStack->Parameters.Read.ByteOffset.LowPart,
    irpStack->Parameters.Read.Length);
  }
  else {
    WriteEvent(MSG_MAJORFUNC_NOT_READ,DeviceObject,NULL);
  }

  IoCompleteRequest(Irp, IO_NO_INCREMENT);
  return STATUS_SUCCESS;
}
A driver should call IoGetCurrentIrpStackLocation in its IRP function to receive a pointer to a IO_STACK_LOCATION structure.
MmGetSystemAddressForMdlSafe is a macro. It returns a virtual address to non system-space for the buffer described by the MDL.

IRP_MJ_WRITE

NTSTATUS WriteCamel(IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp) {
  PUCHAR                      currentAddress;
  PIO_STACK_LOCATION          irpStack;

  if (!driverExtension) {
    IoCompleteRequest(Irp, IO_NO_INCREMENT);
    return STATUS_INSUFFICIENT_RESOURCES;
  }

  irpStack = IoGetCurrentIrpStackLocation(Irp);

  if (irpStack->MajorFunction == IRP_MJ_WRITE) {
    currentAddress = MmGetSystemAddressForMdlSafe(Irp->MdlAddress, NormalPagePriority);

    if (!currentAddress) {
      IoCompleteRequest(Irp, IO_NO_INCREMENT);
      return STATUS_SUCCESS;
    }

    RtlMoveMemory(driverExtension->buffer+irpStack->Parameters.Write.ByteOffset.LowPart,
        currentAddress, irpStack->Parameters.Write.Length);
  }
  else {
    WriteEvent(MSG_MAJORFUNC_NOT_READ,DeviceObject,NULL);
  }

  IoCompleteRequest(Irp, IO_NO_INCREMENT);
  return STATUS_SUCCESS;
}

IRP_MJ_SHUTDOWN

NTSTATUS ShutdownCamel(IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp) {
  WriteEvent(MSG_SHUTDOWN,DeviceObject,NULL);
  IoCompleteRequest(Irp, IO_NO_INCREMENT);
  return STATUS_SUCCESS;
}

IRP_MJ_DEVICE_CONTROL

NTSTATUS IoCtlCamel(IN PDEVICE_OBJECT DeviceObject, IN PIRP Irp) {
  WriteEvent(MSG_IOCTL,DeviceObject,NULL);
  IoCompleteRequest(Irp, IO_NO_INCREMENT);
  return STATUS_SUCCESS;
}

The unload function

VOID CmlUnload (IN PDRIVER_OBJECT  DriverObject) {
  UNICODE_STRING linkString;

  WriteEvent(MSG_DRIVERUNLOAD, DriverObject, NULL);
  ExFreePool(driverExtension);
  RtlInitUnicodeString (&linkString, L"\\DosDevices\\Kamel");
  IoDeleteSymbolicLink (&linkString);
  IoDeleteDevice(DriverObject->DeviceObject);
}

Writing Events from a Device Driver

It is possible to write strings from the driver into the system event box (which then can be viewed with the event viewer (eventvwr.exe). It is not straight forward however and the following steps must each be done.

The Message File

First, a message file must be created, having the suffix .mc, that contains each possible string you want to output and also assignes a unique id to these strings. A sample is given here:
MessageID    = 1
Severity     = Informational
SymbolicName = MSG_DRIVER_ENTRY
Language     = English
Driver Entry
.
MessageID    = 2
Severity     = Informational
SymbolicName = MSG_CREATE
Language     = English
Create
.
Each Entry must be followed by a single dot on its own line. In this sample, the unique Id is associated with the symbolic name MSG_DRIVER_ENTRY and the String "Driver Entry". If you take a look at DriverEntry above, you'll see that I call WriteEvent with the symbolic name MSG_DRIVER_ENTRY.
The Message File then is to be compiled with the message compiler mc: mc KamelMsg.mc on the command line. This produces a file called MessageFile.rc. KamelMsg.rc must be included in the sources file. It also creates the file KamelMsg.h which must be included to have the constants.
This is still not sufficient. Also a string entry must be created in the Registry under HKLM\SYSTEM\CurrentControlSet\Services\Eventlog\System\<driverName>\EventMessageFile. The string must point to the .dll or .sys into which the messages were compiled, in our case: %SystemRoot%\System32\Drivers\Kamel.sys

WriteEvent

BOOLEAN WriteEvent(IN NTSTATUS ErrorCode , IN PVOID IoObject,IN PIRP Irp) {
  PIO_ERROR_LOG_PACKET Packet;
  PIO_STACK_LOCATION IrpStack;
  PWCHAR pInsertionString;
  STRING AnsiInsertString;
  UNICODE_STRING UniInsertString;

  UCHAR PacketSize;

  PacketSize = sizeof(IO_ERROR_LOG_PACKET);

  Packet = IoAllocateErrorLogEntry(IoObject,PacketSize);
  if (Packet == NULL) return FALSE;

  Packet->ErrorCode         = ErrorCode;
  Packet->UniqueErrorValue  = 0,
  Packet->RetryCount        = 0;
  Packet->SequenceNumber    = 0;
  Packet->IoControlCode     = 0;
  Packet->DumpDataSize      = 0;
  
  if (Irp!=NULL) {
     IrpStack=IoGetCurrentIrpStackLocation(Irp);
     Packet->MajorFunctionCode = IrpStack->MajorFunction;
     Packet->FinalStatus = Irp->IoStatus.Status;
  } 
  else {
     Packet->MajorFunctionCode = 0;
     Packet->FinalStatus       = 0;
  }

  IoWriteErrorLogEntry(Packet);
  return TRUE;
}

WriteEvent.h

BOOLEAN WriteEvent(IN NTSTATUS ErrorCode , IN PVOID IoObject,IN PIRP Irp); 
#pragma alloc_text(PAGE, WriteEvent)

Entries in the registry

The driver must be registred with the registry: Create a this key HKLM\System\CurrentControlSet\Services\<driverName> and add the following keys: ErrorControl, Group, Start, Tag and Type.

Feedback

# re: Writing a device driver for Windows  回復  更多評論   

2009-10-30 15:20 by 溪流
mark. thx.
青青草原综合久久大伊人导航_色综合久久天天综合_日日噜噜夜夜狠狠久久丁香五月_热久久这里只有精品
  • <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            亚洲综合精品一区二区| 99riav久久精品riav| 久久手机精品视频| 国产一区二区av| 亚洲欧美在线aaa| 久久精品中文字幕免费mv| 国产日韩在线不卡| 久久亚洲精品中文字幕冲田杏梨| 久久综合亚州| a4yy欧美一区二区三区| 国产精品一区二区久久| 欧美一区影院| 亚洲高清激情| 亚洲免费中文字幕| 亚洲高清视频中文字幕| 欧美成人自拍| 亚洲欧美中文日韩在线| 亚洲国产网站| 在线电影一区| 欧美精品一区二区三区视频| 亚洲一区视频| 亚洲三级免费观看| 免费久久99精品国产自| 夜夜嗨av色综合久久久综合网| 国产精品久久777777毛茸茸| 狼狼综合久久久久综合网| 一区二区三区鲁丝不卡| 欧美激情按摩在线| 久久不见久久见免费视频1| 99精品欧美一区二区三区综合在线 | 欧美一级久久| 亚洲精选中文字幕| 亚洲第一中文字幕| 国产精品观看| 欧美日本一区二区视频在线观看| 久久视频在线视频| 欧美一区在线直播| 亚洲一区激情| 亚洲六月丁香色婷婷综合久久| 久久国产精品毛片| 日韩亚洲精品视频| 狠狠综合久久| 国产乱肥老妇国产一区二| 欧美人成在线| 欧美人成免费网站| 欧美日韩另类国产亚洲欧美一级| 亚洲色诱最新| 亚洲精品1区| 欧美国产免费| 亚洲第一狼人社区| 欧美激情影院| 91久久黄色| 日韩午夜高潮| 中文精品视频一区二区在线观看| 亚洲伦理在线| 99热免费精品在线观看| 亚洲国产视频一区二区| 亚洲国产精品一区二区www在线| 欧美成人在线网站| 免费观看亚洲视频大全| 欧美 日韩 国产在线| 久久影视精品| 亚洲国产精品成人精品| 亚洲精品中文字幕女同| 夜夜嗨av一区二区三区网站四季av | 国产精品日韩一区| 午夜精品久久| 欧美中文字幕视频| 久久精品天堂| 另类欧美日韩国产在线| 亚洲欧美国产一区二区三区| 欧美亚洲三区| 麻豆久久久9性大片| 欧美极品欧美精品欧美视频| 欧美三级电影一区| 国产日本欧美视频| 极品日韩久久| 亚洲免费不卡| 亚洲午夜成aⅴ人片| 欧美亚洲一区三区| 免费精品99久久国产综合精品| 91久久香蕉国产日韩欧美9色| 亚洲美女中出| 亚洲九九九在线观看| 日韩亚洲欧美中文三级| 午夜在线电影亚洲一区| 噜噜噜久久亚洲精品国产品小说| 欧美日韩精品一区视频 | 影音先锋中文字幕一区二区| 亚洲七七久久综合桃花剧情介绍| 99av国产精品欲麻豆| 欧美亚洲综合网| 最新成人在线| 久久国产精品72免费观看| 欧美日韩在线一区二区| 狠狠干综合网| 国一区二区在线观看| 亚洲丝袜av一区| 欧美激情1区2区3区| 欧美综合国产精品久久丁香| 欧美色图天堂网| 亚洲国产精品成人| 欧美一级在线亚洲天堂| 91久久久久久国产精品| 久久都是精品| 国产目拍亚洲精品99久久精品| 最新国产成人在线观看| 久久精品国产在热久久| 亚洲精品免费观看| 欧美电影打屁股sp| 欧美另类视频| 亚洲日本中文字幕| 欧美91福利在线观看| 欧美一级片久久久久久久| 国产精品国产三级国产aⅴ入口| 亚洲精品国产精品国自产观看| 久久精品一级爱片| 午夜精品久久久久久久99黑人| 欧美午夜视频在线观看| av不卡免费看| 亚洲黄色成人| 久久综合久久久| 中文久久乱码一区二区| 久久一区国产| 国产精品久久久久毛片软件| 亚洲视频福利| 亚洲免费观看高清完整版在线观看熊| 久久久亚洲精品一区二区三区| 国产日韩一区| 久久久精品视频成人| 性做久久久久久免费观看欧美| 国产精品成人av性教育| 中文av一区二区| 一区二区三区久久网| 国产精品天天看| 久久视频在线免费观看| 久久精品动漫| 一区精品久久| 欧美成人精品在线| 久久国产精品色婷婷| 亚洲电影天堂av| 亚洲高清一区二区三区| 欧美噜噜久久久xxx| 亚洲影视在线| 久久aⅴ国产欧美74aaa| 精品999在线观看| 亚洲激情影视| 国产精品国产a级| 久久久久成人精品| 老司机精品视频网站| 在线亚洲成人| 欧美一区二区三区四区在线 | 亚洲激情一区二区三区| 欧美激情一区二区三区在线视频| 欧美高潮视频| 先锋a资源在线看亚洲| 久久久久成人精品免费播放动漫| 黄色亚洲大片免费在线观看| 亚洲电影免费在线| 国产精品久久久久国产精品日日| 久久精品一区二区三区四区 | 欧美gay视频激情| 亚洲欧美在线一区二区| 久久精品国产精品亚洲精品| 亚洲福利国产| 亚洲综合精品自拍| 亚洲精品极品| 亚洲欧美日韩中文视频| 亚洲欧洲一区| 久久成人人人人精品欧| 亚洲天堂视频在线观看| 久久久欧美精品sm网站| 宅男噜噜噜66一区二区66| 久久精品噜噜噜成人av农村| 一区二区三区欧美激情| 久久成人这里只有精品| 亚洲欧美国产一区二区三区| 免费日韩精品中文字幕视频在线| 欧美一区二区三区视频在线观看| 欧美精品在线一区| 六十路精品视频| 影音先锋一区| 老巨人导航500精品| 午夜在线一区二区| 欧美日韩免费观看一区三区| 久久精品国产综合精品| 欧美午夜精品久久久久久人妖| 欧美xx视频| 精品999网站| 欧美在线观看一区二区| 午夜精品久久久久久久久| 欧美日韩三级| 亚洲美女91| 亚洲人久久久| 欧美不卡视频一区发布| 久久久亚洲精品一区二区三区| 国产九九视频一区二区三区| 亚洲视频在线观看| 在线日韩中文| 久久综合999|