vdo_enter_read_only_mode(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

βœ¨πŸ’… vdo_enter_read_only_mode(9) πŸ’…βœ¨

okay so this page is from the Kernel API Manual, section 9, and it's all about putting a VDO into read-only mode and saving that read-only state in the super block. bestie, it's giving β€œemergency brake but make it kernel.” 🫢

🌸 NAME 🌸

vdo_enter_read_only_mode β€” Put a VDO into read-only mode and save the read-only state in the super block. πŸ’–

✨ SYNOPSIS ✨

void vdo_enter_read_only_mode (struct vdo *vdo , int error_code );

πŸŽ€ ARGUMENTS πŸŽ€

  • vdo β€” the VDO itself, the main character here. πŸ‘‘
  • error_code β€” the error which caused the VDO to enter read-only mode 😭 that's the reason, no cap.

πŸ¦‹ DESCRIPTION πŸ¦‹

This method is a no-op if the VDO is already read-only. literally nothing happens, bestie β€” it is already read-only, so it stays unbothered πŸ’…βœ¨

🌈 SEE ALSO 🌈

okay the friend group is huge, but we do not skip anyone:


mwah πŸ’‹ this little page comes from the ./drivers/md/dm-vdo source/version, stamped October 2026, and it's literally vdo_enter_read_only_mode(9). bye bestie, slay your kernel debugging! πŸ«ΆπŸ’–

πŸ“¦ where this page comes from