The asynchronous behaviour raises interesting questions as to whether or not this is a bug or working as intended, and whether or not the io_uring API should offer controls to allow the calling application to decide.
With synchronous intra-machine calls we mostly take it for granted that pending modifications die with the caller.
But with inter-machine communications we mostly take it for granted that the sending machine and its entire local area can disappear and operations it sent will complete.
Of course, there are exceptions, especially when APIs/systems offer atomicity, consistency checks, etc.
But without express design intent, or preferably caller intent, one can argue both sides of the asynchronous intra-machine case and be right.
I guess my thinking isn't so much that this happens as that it happens implicitly.
I'm the author and I'm not native speaker, so please bear that in mind. However, I admit I've used AI for grammar and style. IMHO, the post is not fiction, I just wanted to communicate the ideas as clearly and effectively as possible.
Frankly speaking, you are the second (with this thread, the third) one, who says that. So, it looks that I really should write myself again with just grammar checks, not the style.
If you're going for just grammar and spelling, Grammarly has been around for ages and doesn't try to rewrite everything. I'm a native speaker and I don't trust any LLM to retain my style because diffing paragraphs or reworking sections is tedious as hell. I'm reeeeeally lazy and the only workflow I am tempted to do is a rough draft from an LLM, a full rewrite from me, and something like Grammarly for small mistakes. Anything over a single iteration feels like pulling teeth because it's never as subtle as you tell it to be. It truly feels like giving a typewriter to monkeys.
What I've done a few times is have the AI provide feedback, and then I rewrite myself based on the feedback. So I don't use what the AI suggests directly, just the essence if I agree.
That's a good approach. My sin is that if I like the sentence, I keep and don't rewrite. Because if I see it is good, I don't feel I should. And probably I don't see that "prose" is bad each time it is indeed bad.
Maybe you should just patch a grammar problem instead of rewriting the whole sentence. (I'm not blaming you but just sharing my experience, I suspect your first language might be a Slavic one like mine.)
Well, to be completely honest with you, it is obvious in your comments here. But my point was, keeping your Slavic accent and fixing the most glaring places with the help of AI is probably better than letting AI rewrite large portions of your text into "Better English". People do hate the AI accent these days, you know.
If it's truly asynchronous, I don't see the issue with IO being decoupled from process lifetime.
If you wanted to stop the IO at process death, the mechanism needed for this would introduce an overhead that would likely slow things down in general.
Can you explain your thinking? As an extreme example you could have a "write backdoored .bashrc, then wait 5 minutes" repeated a thousand times queued as async i/o. If malware did this you couldn't just kill the process to stop it. You would have to shutdown the machine.
Note, that this also includes retaining process memory related to the I/O. In my experiment I used regular 4 KiB pages, which is smaller or equal to the I/O block size. However, in case of huge pages only a small fraction can be I/O related. And I suppose, that this small part would pin the whole page, which might have some sensitive information. Still protected, however, but who knows.
Unrelated: My cat died. Saddest day of my life. I watched the light leave his eyes and still wonder where he went.
I looked it up and it said that the last thing to go when dying is probably your hearing.
When you die, typically you lose your sight first, then your bodily sensations, and 1-by-1 all your sensory channels turn off: Balance, equilibrium, proprioception, until you are like an empty force flying through infinite darkness, all your thoughts still in tact, knowing what is happening to you, and in the background you can still hear everyone in the room, until the sounds too begin to fade and distort into a light buzzing noise that gets higher and higher pitched like a zipper zipping up your last waking experience in a metaphorical body bag to be tossed off the edge of time.
With synchronous intra-machine calls we mostly take it for granted that pending modifications die with the caller.
But with inter-machine communications we mostly take it for granted that the sending machine and its entire local area can disappear and operations it sent will complete.
Of course, there are exceptions, especially when APIs/systems offer atomicity, consistency checks, etc.
But without express design intent, or preferably caller intent, one can argue both sides of the asynchronous intra-machine case and be right.
I guess my thinking isn't so much that this happens as that it happens implicitly.
> These are measured results backed by the Linux source, not a portable guarantee for every kernel, filesystem, device, or API called “AIO”.
> The interesting race window is there, but hard to see. So I made it larger.
Or that they want AI text over imperfect English
Hilarity may ensure.
If you wanted to stop the IO at process death, the mechanism needed for this would introduce an overhead that would likely slow things down in general.
Unrelated: My cat died. Saddest day of my life. I watched the light leave his eyes and still wonder where he went.
I looked it up and it said that the last thing to go when dying is probably your hearing.
When you die, typically you lose your sight first, then your bodily sensations, and 1-by-1 all your sensory channels turn off: Balance, equilibrium, proprioception, until you are like an empty force flying through infinite darkness, all your thoughts still in tact, knowing what is happening to you, and in the background you can still hear everyone in the room, until the sounds too begin to fade and distort into a light buzzing noise that gets higher and higher pitched like a zipper zipping up your last waking experience in a metaphorical body bag to be tossed off the edge of time.