vm-memory is really cool and should be IMHO part of stdlib :-) best way to map files and other memory so far in #Rust.

Some project types where you absolutely need memory mapped I/O are:

• Operating Systems
• Database Management Systems
• Virtual Machine Managers
• Game Engines
• Digital Audio Workstations

I.e. anything with high scalability, high availability and in real-time processing low latency.

#rustlang

@ljs Thanks mate! Yeah, and I thought that if this makes anyone feeling bad of not doing the exercise, it is actually good :-)

Week #2 lifting weigths done after two year break. Since I have to post this, it is not a routine yet 🙂Feeling better than in ages and peace in mind. #detox

@laund @calbaker ok cool, i'm fine with being stupid beyond the scope of "none yet" ;-) no reason to get upset tbh.

@calbaker @laund E.g. it is proved that the problem of "zero bugs" cannot be proved except when you have some well defined constraints which is basis of formal verification. In generic case, i.e. Rust app ecosystem we are talking numerically infinite set of programs with no constraints except those that computational model of Turing machine sets.

@calbaker @laund It is pretty weird to see comments that fight against lemmas that have been proved by computer science decades ago. As if Rust was yet another computational model, e.g. in same level as turing machines and quantum computation.

@calbaker @laund Yeah, Rust is great and for any non-legacy fresh new project that I had previously written in C or C++ I would pick it any day.

It just that I consider it harmful thinking that problems are solved by tools. Rust can bring the edge but it needs to be supported understanding its shortcomings, limits, CPU architecture, binary formats (ELF, COFF/PE) and various other domain assets. Rust alone is not a problem solver. So it is important to raise attention on this issue.

Huge issue in #riscv specifiations is the lack of pseudocode. E.g. this is from the description of SWI opcode:

"The Wait for Interrupt instruction (WFI) provides a hint to the implementation that the current hart can be stalled until an interrupt might need servicing. Execution of the WFI instruction can also be used to inform the hardware platform that suitable interrupts should preferentially be routed to this hart."

Any ideas what actuallly happens when WFI is executed? I don't know. For x86 I just find the opcode from Intel SDM, and then I just read the pseudocode. I usually do not even read the prose unless really need to get bottom of it.

Hey folks,

Danke für all the support. You can save 15% on everything on #BandcampFriday today, when you use the discount code "DANKE" at checkout, from today until Monday!

👉 https://polarity.bandcamp.com/

#musodon #music #bandcamp

@matzipan @calbaker We could not know that because now you are talking about the famous halting problem in computer science or at least something that can be mapped into it as bijection between the sets.

@argv_minus_one Also, you are essentially now disagreeing on that Rust is not feature. I.e. you are agreeing on that Rust is a feature 🤷

@calbaker That said obviously those checks that exist given the validation make the injection harder but I would not hold my breath seeing a Rust program used in volumes with zero CVE's in its life-cycle. That has never happened in history of security vulnerabilities so far.

@argv_minus_one Such language that would be memory safe does not exist.

@calbaker No.

It has static and run-time checks for memory safety, which is not the same as being memory safe. Just like Go, Java, Python and what not have measures for memory safety but instead of borrow checker they use a garbage collector.

Rust is less safe than any of those languages because the result is an ELF binary, which is roughly a twist of what C++ source generates with fancy checks. Same attack techniques, like ROP (return-oriented programming) gadgets still apply as for any possible ELF binary ever compiled.

When promoting apps, it is good to remember that #Rust is not a #feature :-) I zero care what language is used. Programming language is only a recipe. A CPU has only one single language that it runs baked from that recipe.

Or actually I do care in the sense that it is a huge turn back. It is misguided advertisement by definition because a competing app might not have this artificial feature. Some casual users might even think that an app is somehow better because it has the imaginary performance improvement thanks to Rust.

#rustlang

Don’t you see why many Americans see such talk of dictatorship as contrary to our most cherished principles? Trump says no. Quite the opposite, he insists. “I think a lot of people like it.” -Trump in https://time.com/6972021/donald-trump-2024-election-interview/

Not my vote so no further comments. I just imagine that I did not read this 🤷

#democracy

[$] Inheritable credentials for directory file descriptors https://lwn.net/Articles/971825/ #LWN

Despite the misleading name, apparently rust-vmm/vm-memory can do memory mapped I/O on a wider scope. I.e. it could be used in a project having nothing to do with virtualization. In Enarx the situation is two-folded:

• SGX needs device memory maps
• KVM based confidential computing needs whatever the name of “the thing” providing private memory areas is ATM through KVM shenanigans ;-) Have to check.

Posted #enarx issue: https://github.com/enarx/enarx/issues/2580 #rust #rustlang

WhatsApp Spam has been increasingly annoying recently, how can someone be calling me on WhatsApp that ISN'T a WhatsApp user?