smukherjee19
Joined 7 years ago
Karma
732
Submissions
113
Member since
Sep 30
Recent submissions
Comment · 2 days ago
Good findings, but the findings are so AI-generated and hard to read… Feels like I am being thrown numbers without a coherent story, and even worse, with beautiful animations which only serves as distraction…
This looks very similar to the diary entries my LLM writes when working on a coding project.
Comment · 22 days ago
Stereotyping mathematicians, well played sir.
Comment · 1 month ago
I wonder if this paper has been peer-reviewed at a decent conference/journal.
Comment · 3 months ago
OP here. Thank you so much for taking the time to write it!
This is so much easier to understand, and I also learnt a few things along the way, like the zero page mechanism, munmap having to notify the MMU about the invalid TLB and more.
Really appreciate it!
Comment · 3 months ago
Unfortunately, the kernel bug would need to be understood to be patched, and the developed patch itself would need to be reviewed before being accepted, which seems... very hard, to put it mildly, using the nails-on-chalkboard LLM spew report.
Comment · 3 months ago
Thanks for the explanation. I should have looked up each term a bit more.
So "backing" is the underlying physical memory the page maps to.
So if I were to make sense of that piece of slop, is this what it would be?
"In one thread, a page fault happens during a store operation. The physical memory address is the proper address, which is immediately (around 10 assembly instructions later) replaced by the 0x00000000 memory address by another thread due to race condition, resulting in a crash when the original thread tries to read that page again."
Comment · 3 months ago
I tried reading and gave up at the "Headline"...
Quoting from the bug analysis:
>Headline. The crash is real and reproducible. With musl instrumentation we pin the in-process mechanism precisely: a thread's own store to a freshly- faulted anonymous page becomes invisible to that same thread's reload ~10 instructions later, because the page's backing is replaced mid-function. A pagemap read at the instant of the fault shows the backing is the kernel's zero page. A captured core dump confirms the crash site with matched virtual addresses. The mechanism localizes to the interaction between the per-VMA-lock anonymous-fault fast path and a concurrent munmap's TLB shootdown. A source-level review of Linux 7.0.12 identifies a specific race in that interaction, and a git comparison across v6.19/v7.0/v7.1/mainline identifies the v7.0-introduced change on the munmap-teardown side that widens it.
"a thread's own store to a freshly- faulted anonymous page becomes invisible to that same thread's reload ~10 instructions later, because the page's backing is replaced mid-function." -> ??? What's a "backing" of a page? Freshly-faulted? Fresh fries? "~10 instructions later"?
"A pagemap read at the instant of the fault shows the backing is the kernel's zero page." -> Backing?
"The mechanism localizes to the interaction between the per-VMA-lock anonymous-fault fast path and a concurrent munmap's TLB shootdown." -> How can a mechanism "localize"?
And more.
This is... words strung together. Nothing more. I wonder how people read and make sense of this.
In case people have forgotten what real technical writing looks like, here's a sample (I am not the author): https://yifan.lu/2019/01/11/the-first-f00d-exploit/
Comment · 4 months ago
Clickbait and aggressive title, shallow article. I read it and not worth clicking.
Comment · 5 months ago
That's weird. I use Gmail regularly and did not experience anything like that; it works just the way it did for the past 10+ years. And auto categorization still works just fine, and no AI summarizing my email or trying to write my drafts. I wonder what difference we have in settings.
Also, not to be disrespectful to the OP, but seems quite an... overblown reaction. To each their own, though.
Comment · 7 months ago
Just a guess, with Macbook Neo releasing, M$ likely got scared of mass exodus to MacOS (the average PC user can now consider a Macbook and it likely wipes the floor with all Windows laptops out there) and decided to throw in a damage control piece.
Comment · 7 months ago
Yes, especially if people living in the city. I have known Japanese people who can’t speak English well but can read technical CS papers and understand well enough to give a summary and presentation in Japanese.
Just keep in mind they are usually very good in reading, okayish in listening, and kinda needs work on speaking. But that’s expected. If you live a daily life in Japan like the Japanese, you barely need to speak English, or hear it, if at all. Even the foreign staff at the convenience store speak Japanese good enough for them to carry on their duties.