Crate nt_list 

Provides compatible, type-safe, and idiomatic Rust implementations of the Windows NT Linked Lists, known as LIST_ENTRY and SINGLE_LIST_ENTRY.

Singly and doubly linked lists of this format are fundamental data structures widely used in Windows itself and in drivers written for Windows. In the case of a doubly linked list, Windows defines a LIST_ENTRY structure with forward and backward pointers to other LIST_ENTRY structures. LIST_ENTRY is then embedded into your own element structure. Check the relevant Microsoft documentation for more details on linked lists in Windows.

This design exhibits several properties that differ from textbook linked list implementations:

• A single element can be part of multiple lists (by having multiple LIST_ENTRY fields).
• YOU are responsible for pushing only elements of the same type to a list. Without any type safety, the C/C++ compiler cannot prevent you from adding differently typed elements to the same list.
• Links point to the LIST_ENTRY field of an element and not to the element itself. YOU need to retrieve the corresponding element structure using CONTAINING_RECORD, and it’s YOUR responsibility to use the correct parameters for that macro.

The nt-list crate introduces type safety for these lists, taking away some responsibility from the user and moving it to the compiler. Additionally, it offers an idiomatic Rust interface similar to that of LinkedList and Vec.

Example

Creating a linked list with nt-list boils down to these three steps:

1. You define an empty enum to identify your list (for type safety when pushing elements), and derive either NtList (doubly linked list) or NtSingleList (singly linked list).
2. You define your element structure, declare an entry as #[boxed] if desired, and derive NtListElement.
3. You call new of the respective list implementation with the element structure and empty enum as type parameters.

All of this taken together looks like:

#[derive(NtSingleList)]
enum MyList {}

#[derive(Default, NtListElement)]
#[repr(C)]
struct MyElement {
    #[boxed]
    entry: NtSingleListEntry<Self, MyList>,
    value: i32,
}

fn test() {
    let mut list = NtBoxingSingleListHead::<MyElement, MyList>::new();

    list.push_front(MyElement {
        value: 42,
        ..Default::default()
    });

    for element in list.iter() {
        println!("{}", element.value);
    }
}

Check the module-level documentation of list and single_list for more information on how to use nt-list.

no_std support

The crate is no_std-compatible and therefore usable from firmware-level code up to user-mode applications.

To support heap allocations in NtBoxingListHead and NtBoxingSingleListHead, the crate depends on the alloc library. If you want to use the crate in a pure no_std environment without heap allocations, include it with default-features = false to disable the default alloc feature.

Modules

list

A doubly linked list compatible to LIST_ENTRY of the Windows NT API.

single_list

A singly linked list compatible to SINGLE_LIST_ENTRY of the Windows NT API.

Traits

NtBoxedListElement

Enables NtBoxingListHead for a list element structure.

NtListElement

Designates a structure as a list element with an entry field (e.g. NtListEntry) of a particular NT list. The entry field’s position inside the list is given by implementing the offset method. The NT list is identified via the enum that implements NtTypedList.

NtListType

The type (singly or doubly linked list) of an empty enum that implements NtTypedList.

NtTypedList

Designates an empty enum as an NT list of a specific type (singly or doubly linked list).

Derive Macros

NtListElement

Implements the NtListElement and (optionally) NtBoxedListElement traits for the given element structure.