STRUCT RNBD_MSG_CLOSE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ struct rnbd_msg_close(9) ✨

okay so bestie, welcome to the struct rnbd_msg_close page from the Kernel API Manual πŸ’… this one's a tiny lil cutie and honestly? it's giving "small but mighty." it's the request to close a remote device, periodt πŸŽ€


🌸 NAME 🌸

struct rnbd_msg_close β€” the request to close a remote device. that's it, that's the whole vibe πŸ¦‹


⭐ SYNOPSIS ⭐

here's the whole shape of it, no notes, literally exactly this:

struct rnbd_msg_close {
    struct rnbd_msg_hdr hdr;
    __le32 device_id;
 };

(two members. that's the entire struct. she's lowkey minimal and we respect that πŸ™ˆ)


πŸŽ€ Members πŸŽ€

  • hdr β€” the message header, bestie. the standard lil header situation every message carries 🫢
  • device_id β€” the device_id on the server side, which is how the server identifies the device. iykyk πŸ‘‘

πŸ”₯ SEE ALSO πŸ”₯

go read these next, fr fr β€” they're all in the kernel file ./drivers/block/rnbd/rnbd-proto.h:

  • enum rnbd_msg_type(9)
  • struct rnbd_msg_hdr(9)
  • struct rnbd_msg_sess_info(9)
  • struct rnbd_msg_sess_info_rsp(9)
  • struct rnbd_msg_open(9)
  • struct rnbd_msg_open_rsp(9)
  • struct rnbd_msg_io(9)
  • enum rnbd_io_flags(9)

like. that's the whole friend group and they all slay in their own way 🌈


aaaand that's the page!! you ate that πŸ’– this whole thing lives over in ./drivers/block/rnbd, dated October 2026, and the title is (you guessed it) struct rnbd_msg_close(9) β€” mwah, go close some remote devices responsibly, bestie 😭🌸

πŸ“¦ where this page comes from