Promote Sign in Sign up

[$] Fixing the TCMalloc regression with RSEQ operations

corbet LWN.net 2026-09-07 22:33 8 views

The restartable sequences feature is one of the stranger corners of the kernel's user-space interface; it provides a way for user space to carry out simple lockless operations and be informed if it is preempted over the course of an operation (and must, thus, restart). Work merged in the 6.19 release to improve the performance of restartable sequences broke the TCMalloc allocator, which was relying on an undocumented (and unintended) kernel behavior. Now, Olivier Dion is proposing an addition to the restartable-sequences API that will bring TCMalloc back into the fold; it does not make the restartable-sequences API any less strange, though.

Read original: https://lwn.net/Articles/1092555/

My Favorites →

← Previous From Prompt to Paycheck: Wiring an LLM Chain Into Real Gig Platforms Next → Opacity within variables, and how it affects a shadcn design system token implementation

Zero-Budget Web Dev: Moving from Discord/Drive to Google Sites

Welcome to part one! This is the start of a series where I’ll be posting about my webdev and HTML nightmares. I hope you enjoy the read as much as I hate User Interfaces! Consider this a shared space for learning—I’m sharing what I’ve learned so far, and I’d love to hear your thoughts or better so

Frontend 09-08 2 DEV Community

My adaptive memory stayed empty in production, and it wasn't a bug

I had a table in the database that was supposed to fill itself. Its job was to learn from failures: every time the system tried a variant of something and it didn't work, it saved it, to recycle later in another context where it might. A laboratory of failed attempts, piling up. In production it ha

Frontend 09-08 2 DEV Community

MV3 Chrome Extensions — Everything That Broke and How I Fixed It

When I started building TokenPulse as a Manifest V3 extension, I knew MV3 was stricter than MV2. I did not know how many things would break silently, produce cryptic errors, or fail only in production. Here is every significant MV3 problem I hit and how I fixed each one. Problem 1: Inline

Frontend 09-08 3 Dev.to (EN Zone)

Authentication APIs Explained: Template-Owned US/EU Login OTP with SMS and Email Fallback

Short answer: choose an SMS-first authentication messaging API with direct OTP start and verification calls when you own the login templates and need US/EU delivery; keep email as an application-managed fallback, and choose a managed multichannel verification product instead if SMTP relay, voice, Wh

Frontend 09-08 6 Dev.to (EN Zone)

Comments0

No comments yet — be the first