Android's new Bluetooth stack rewrite (Gabeldorsh) is written with Rust
android.googlesource.com
Android's new Bluetooth stack rewrite (Gabeldorsh) is written with Rust
1–10 of 393 posts
Re: Android's new Bluetooth stack rewrite (Gabeldorsh) is written with Rust
#2Zach, if you're reading this, HUGE kudos to holding the line in replacing that, and double kudos for doing it in a verifiable, sane language!
Re: Android's new Bluetooth stack rewrite (Gabeldorsh) is written with Rust
#3Re: Android's new Bluetooth stack rewrite (Gabeldorsh) is written with Rust
#4Re: Android's new Bluetooth stack rewrite (Gabeldorsh) is written with Rust
#5Is this because of memory bugs\vulnerabilities that target the stack or just because it was too old and junky?
Re: Android's new Bluetooth stack rewrite (Gabeldorsh) is written with Rust
#6Is this because of memory bugs\vulnerabilities that target the stack or just because it was too old and junky?
Junkiness and vulnerabilities go hand in hand.
Re: Android's new Bluetooth stack rewrite (Gabeldorsh) is written with Rust
#7I know the guy that heads up the team that did this work -- he and I spent 2+ years fighting Broadcom's old, god-awful bluetooth code. Our whole team used to play what-if games about replacing the thing while massive code dumps came in from vendors, making the task ever larger. Zach, if you're reading this, HUGE kudos to holding the line in replacing that, and double kudos for doing it in a verifiable, sane language!
Re: Android's new Bluetooth stack rewrite (Gabeldorsh) is written with Rust
#8Earlier quoted context omitted.
Junkiness and vulnerabilities go hand in hand.
True that. maybe I'll rephrase, was Rust specifically chosen to address memory concerns? I don't think it is too common in Android.
Re: Android's new Bluetooth stack rewrite (Gabeldorsh) is written with Rust
#9Re: Android's new Bluetooth stack rewrite (Gabeldorsh) is written with Rust
#10I know the guy that heads up the team that did this work -- he and I spent 2+ years fighting Broadcom's old, god-awful bluetooth code. Our whole team used to play what-if games about replacing the thing while massive code dumps came in from vendors, making the task ever larger. Zach, if you're reading this, HUGE kudos to holding the line in replacing that, and double kudos for doing it in a verifiable, sane language!
Correction: god-awful host side bluetooth code.
There is still the bluetooth firmware residing on the BCMxxx chip (or Qualcomm chip) - >1MB of god-awfulerer closed-source code, half of it is in ROM (with limited number of available patch slots), full of bugs. You can see it crash from time to time in the kernel debug logs (and auto-restart itself)