{"id":369,"date":"2024-04-29T15:32:30","date_gmt":"2024-04-29T13:32:30","guid":{"rendered":"https:\/\/bowfinger.de\/blog\/?p=369"},"modified":"2024-04-29T15:44:37","modified_gmt":"2024-04-29T13:44:37","slug":"working-on-ldd3s-tiny-tty-example","status":"publish","type":"post","link":"https:\/\/bowfinger.de\/blog\/2024\/04\/working-on-ldd3s-tiny-tty-example\/","title":{"rendered":"Working on LDD3’s tiny tty example"},"content":{"rendered":"\n

A while back I started tipping my toes into Linux Kernel module development. Mainly, to understand a driver for a data capture card I got to work with (or for, I believe).<\/p>\n\n\n\n

Well, there is a go-to reference: the book Linux Device Drivers<\/em>, 3rd Edition by Corbet, Rubini and Kroah-Hartman (from now on LDD3).<\/p>\n\n\n\n

It’s great, it explains a lot and contains lots of hands-on example code<\/a>, too. But, unfortunately it refers to the 2.6 Linux kernel. We’re at 6.8 at the time of writing this. So it’s a bit outdated.<\/p>\n\n\n\n

No worries though, FOSS is a beautiful beast, and people have taken the example modules and updated them<\/a>. Around version 5.15 that is. And things have changed again – at least for tty<\/code> it seems.<\/p>\n\n\n\n

There is a pull request to make it 6.x compatible<\/a>, but … it’s almost a year old by now, and it seems incomplete. Yet, it was a really great thing to come across at the start of this journey, because it restored my sanity.<\/p>\n\n\n\n

So, here’s my go at the tiny tty example driver and I hope I can finish it up into something that works with a 6.x Linux kernel.<\/p>\n\n\n\n

Things have changed<\/h2>\n\n\n\n

Using static major\/minor numbers is discouraged, or at least, made easier to avoid in more recent kernel versions (feels like since 4.x or so). So, some functions used in LDD3’s examples simply don’t exist anymore.<\/p>\n\n\n\n

alloc_tty_driver<\/code> is now superseeded by tty_alloc_driver<\/code> (okay, that re-naming is kind of evil). And while the former only bothered about the number of supported ports, the latter wants flags, too. So, it looks like the returned struct of type tty_driver<\/code> already contains a lot of entries when tty_alloc_driver<\/code> is done with it.<\/p>\n\n\n\n

I’ve refrained from using the TTY_DRIVER_NO_DEVFS<\/code> flag, because I think dynamic stuff is always nice, so TTY_DRIVER_DYNAMIC_DEV<\/code> it is.<\/p>\n\n\n\n

tty_driver->owner<\/code> is not supposed to be set anymore, according to this old’ish LKLM post<\/a>. Same goes for ->major<\/code> (see tty_alloc_driver<\/code>).<\/p>\n\n\n\n

The module is not put down anymore by put_tty_driver<\/code> but by tty_driver_kref_put<\/code> which seemingly also handles references in proc<\/code> (I’ve run into issues that the proc<\/code> entry was not removed after rmmod<\/code>ing the module and hence, on the next try insmod<\/code> was complaining).<\/p>\n\n\n\n

I mention this, because LDD3’s static void __exit tiny_exit(void)<\/code> spends two thirds of its code to close ports and kfree<\/code> associated memory. This code is still present in the pull request with the updated example from 2023.<\/p>\n\n\n\n

Still, I have to investigate if tty_driver_kref_put<\/code> also removes timers.<\/p>\n\n\n\n

Things have gotten easier<\/h2>\n\n\n\n

Compared to the example for a 2.6 kernel in LDD3, the current version (at least for module __init<\/code> and __exit<\/code>) is way easier and frankly cleaner, i.e. easier to read.<\/p>\n\n\n\n

Still, or maybe exactly because of that<\/em>, I think it’s time for a fourth edition of Linux Device Drivers<\/em>.<\/p>\n\n\n\n

I try to go through with the rest of the module and understand and ideally fix it. Then I’ll upload it too, for later generations at kernel 8.x to despair of it. Link soon.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

A while back I started tipping my toes into Linux Kernel module development. Mainly, to understand a driver for a data capture card I got to work with (or for, I believe). Well, there is a go-to reference: the book Linux Device Drivers, 3rd Edition by Corbet, Rubini and Kroah-Hartman (from now on LDD3). It’s…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[17,16],"tags":[94,97,95,18,96,98],"class_list":["post-369","post","type-post","status-publish","format-standard","hentry","category-hardware","category-linux","tag-driver","tag-example","tag-kernel","tag-linux","tag-tty","tag-tutorial"],"_links":{"self":[{"href":"https:\/\/bowfinger.de\/blog\/wp-json\/wp\/v2\/posts\/369","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bowfinger.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bowfinger.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bowfinger.de\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/bowfinger.de\/blog\/wp-json\/wp\/v2\/comments?post=369"}],"version-history":[{"count":2,"href":"https:\/\/bowfinger.de\/blog\/wp-json\/wp\/v2\/posts\/369\/revisions"}],"predecessor-version":[{"id":372,"href":"https:\/\/bowfinger.de\/blog\/wp-json\/wp\/v2\/posts\/369\/revisions\/372"}],"wp:attachment":[{"href":"https:\/\/bowfinger.de\/blog\/wp-json\/wp\/v2\/media?parent=369"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bowfinger.de\/blog\/wp-json\/wp\/v2\/categories?post=369"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bowfinger.de\/blog\/wp-json\/wp\/v2\/tags?post=369"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}