drbd_send_state(9)

💅 drbd_send_state(9) 💅

hey bestie, welcome to the Kernel API Manual — today’s main character is drbd_send_state(9), and it’s literally all about sending the new state to the peer after a state change. 🦋

---

💖 NAME 💖

drbd_send_state — after a state change, sends the new state to the peer. periodt. ✨

---

✨ SYNOPSIS ✨

int drbd_send_state (struct drbd_peer_device *peer_device , union
drbd_state state );

---

🎀 ARGUMENTS 🎀

• peer_device — DRBD peer device. 🫶
• state — the state to send; not necessarily the current state. 👑

---

🦋 DESCRIPTION 🦋

okay so here’s the tea: each state change queues an "after_state_ch" work, and that work will eventually send the resulting new state to the peer. 💌

if more state changes happen between queuing and processing of the after_state_ch work, we still want to send each intermediary state in the order it occurred. the timeline stays intact, no cap. 🕰️✨

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/block/drbd/drbd_main.c, plus these lil icons:

• tl_release(9)
• _tl_restart(9)
• tl_clear(9)
• tl_abort_disk_io(9)
• drbd_thread_current_set_cpu(9)
• drbd_send_current_state(9)
• _drbd_send_ack(9)
• drbd_send_ack(9)
• drbd_md_sync(9)
• drbd_md_read(9)
• drbd_md_mark_dirty(9)
• drbd_uuid_new_current(9)
• drbd_bmio_set_n_write(9)
• drbd_bmio_clear_n_write(9)
• drbd_queue_bitmap_io(9)
• drbd_bitmap_io(9)
• drbd_wait_misc(9)

---

xoxo, your kernel bestie 💖 — straight from ./drivers/block/drbd, October 2026. 🎀