Viewing profile — mustache_kimono
mustache_kimono
HN member- Joined
- Wed, Jan 24, 2018, 7:32 AM UTC
- HN karma
- 3,836
- Public activity
- 845 items
- HN profile
- View on Hacker News ↗
About mustache_kimono
No profile information was provided.
Recent public activity
-
comment
Comment #49100146
[flagged]
-
comment
Comment #48852831
Wow, yeah, really hate this.
-
comment
Comment #48078397
> Now it needs to be put into shape so that all the unsafe blocks are eliminated All the unsafe seems to be FFI? https://github.com/search?q=repo%3Aoven-sh%2Fbun+unsafe+lang... > a…
-
comment
Comment #47270568
> Why not use a struct of arrays? I would assume because then the shape of the data would be too different? SOAs is super effective when it suits the shape of the data. Here, the d…
-
comment
Comment #46693648
> The two obvious examples Appreciate this rincebrain. Know that you know better than most and this certainly covers my 2nd point. I don't imagine these cases cover my first point …
-
comment
Comment #46693154
> Two examples that I can find I think you may be misreading my point above. I am not arguing ZFS doesn't have bugs. That's nuts. I am arguing that the bug the parent says he has w…
-
comment
Comment #46693098
> There's been several instances. I think you're missing the 2nd feature to the parent's point that I take issue with, which is this is not just a bug that a scrub wouldn't find , …
-
comment
Comment #46693039
> Scrubs check hashes, not structure. How is the structure not valid here? Can you explain to us how an fsck would discover this bug (show an example where an fsck fixed a similar …
-
comment
Comment #46689067
> Imagine that a directory ZAP has an entry that points to a bogus object ID. That would be an example. The ZAP block is intact but its content is inconsistent. The above is intere…
-
comment
Comment #46688818
> Imagine a race condition that writes a file node where a directory node should be. You have a valid object with a valid checksum, but it's hooked into the wrong place in your dat…
-
comment
Comment #46688687
"Scrubs differ significantly from traditional filesystem checks. Tools such as fsck or chkdsk examine logical structures and attempt to repair inconsistencies related to directory …
-
comment
Comment #46651793
> That will also put it on the unfortunate position of being the place that breaks every time somebody adds a bug to the C code. Can someone explain charitably what the poster is g…
-
comment
Comment #46624703
> Why would I use it for s3? You have it the wrong way around. Here, ZFS uses many small S3 objects as the storage substrate, rather than physical disks. The value proposition is t…
-
comment
Comment #46458016
> I think that companies like Oracle, SAP, and Broadcom begin to resemble specialized private equity firms This is an entirely fair/accurate. I suppose what I am getting at is that…
-
comment
Comment #46457858
The next sentence is more defensible: >> Certainly, these companies not endure as innovators: when coercion is your business model, innovation is not merely unnecessary but activel…
-
comment
Comment #46438896
> Page management isn't really a thing we can do well "in user space". But it is the thing most high performance OLTP DBMSs, most of us are aware of, do? I'm also not sure your cit…
-
comment
Comment #46436988
> On performance: ... In particular I am thinking how there's a whole body of research of database buffer pool management Why? The solution thus far has been to turn off what the k…
-
comment
Comment #46436489
> there are many of us who are very thankful for them. Why? Can you explain, in light of the article, and for those of us who may not be familiar with qubes-mirage-firewall, why?
-
comment
Comment #46435970
Bryan Cantrill, "Unikernels are unfit for production". [0] [0]: https://www.tritondatacenter.com/blog/unikernels-are-unfit-f...
-
comment
Comment #46330588
> I think Rust is more unsafe than C due to supply chain issues in the Rust ecosystem This is such an incredibly cheap shot. First, the supply chain issues referenced have nothing …
-
comment
Comment #46318552
> I'm more interested in the % of rust code that is marked unsafe. I think you should less interested in % unsafe as what the unsafe is used to do, that is, it's likelihood to caus…
-
comment
Comment #46308309
> Your sense seems more than a little unrigorous. 1/160 = 0.00625. So, several orders of magnitude fewer CVEs per line of code. This is incorrect. Chalk it up to the flu and fever!…
-
comment
Comment #46305562
> Github says 0.3% of the kernel code is Rust. But even normalized to lines of code, I think counting CVEs would not measure anything meaningful. Your sense seems more than a littl…
-
comment
Comment #46304710
> So the prediction that incautious and unverified unsafe {} blocks would cause CVEs seems entirely accurate. This is one/the first CVE caused by a mistake made using unsafe Rust. …
-
comment
Comment #46237225
> You don't generally need specific versions of GCC or Clang to build it I'm pretty sure. You need a C11 compiler these days with loads of non-standard extensions. Note, for a very…