tty_open_current_tty(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 tty_open_current_tty(9) 🎀

okay bestie, welcome to the Kernel API Manual entry for tty_open_current_tty — this is a little function that hands you back the locked tty of whatever task is currently running, but ONLY if the device you passed in is /dev/tty. no cap. let's get into it 💅

✨ NAME ✨

tty_open_current_tty — get the locked tty of the current task, bestie 🫶

🌸 SYNOPSIS 🌸

struct tty_struct * tty_open_current_tty (dev_t device , struct file *filp );

🦋 ARGUMENTS 🦋

  • device — the device number, like literally the number of the device 🎀
  • filp — a file pointer to the tty ✨

👑 RETURN 👑

returns the locked tty of the current task — but ONLY iff (yes, "iff", the math-y iff, iconic) device is /dev/tty 💖

🌈 DESCRIPTION 🌈

so what it actually does 👀 — it performs a re-open of the current task's controlling tty. that's the whole vibe.

now here's the messy part, and it's giving "why though" 😭 — we cannot return driver and index like we do for the other nodes, because devpts will not work then. it expects inodes to be from devpts FS. periodt. that's the constraint, no workarounds, that's just how it is 🧚

⭐ SEE ALSO ⭐

kernel file ./drivers/tty/tty_io.c — go look, iykyk 🔥

and now the full squad of related functions, all of them, in order, no one left behind 💜:

and that's the whole page, bestie!! 🎀 this lil drop lives down in ./drivers/tty and it's dated October 2026 — so like, future vibes only 🌈✨ thanks for reading, mwah 💋

📦 where this page comes from