senozhatsky

5 ms·

1.
by senozhatsky 2y ago
That's sort of how Linux kernel trace-events are implemented [1]. E.g. DECLARE_EVENT_CLASS(sched_wakeup_template, TP_PROTO(struct task_struct *p), TP_ARGS(__perf_task(p)), TP_STRUCT__entry(
2.
by senozhatsky 2y ago
I wish they offered a paid version of the browser that would have ublock enabled.
3.
by senozhatsky 3y ago
> meaning no local variables (still heavy usage of push/pop within a procedure, does this count as a local?) Isn't it (push/pop) how locals basically work?
4.
Microsoft Was Betting on Unix(twitter.com)
1 points by senozhatsky 4y ago|2 comments
5.
by senozhatsky 6y ago
Knuth's MIX computer with its 6-bit bytes and 5-byte words (IIRC) came to my mind [0] [0] https://en.wikipedia.org/wiki/MIX
6.
by senozhatsky 7y ago
OK, understood. So what you meant was more like puts()'s attack surface is smaller than printf()'s. This is not how your message appeared to me - "printf() is vulnerable to injections, use puts() instead". Both a
7.
by senozhatsky 7y ago
Looks even better!
8.
by senozhatsky 7y ago
Good point. I suppose that you are talking about overwriting terminating NUL, do I get it right? puts() is vulnurable in exactly same way.
9.
by senozhatsky 7y ago
> No. You don't really want to do that. If you're doing that, use puts This is not the case for RO strings, is it?
10.
by senozhatsky 7y ago
I see. So when for a char pointer one needs to do printf("%p\n", v); the Generic call must look like this displayln((const void *)v); is it really better?
11.
by senozhatsky 7y ago
Could be. But wouldn't then displayln() require the same string placeholder? Be it "%s", or "{1}" or someting else.
12.
by senozhatsky 7y ago
> printf("%s\n", "Hello, World!"); > > That's an awful lot of symbolic syntax. Well... Because it should have been printf("Hello, World!\n"); in the first place? One can do
13.
by senozhatsky 7y ago
I think Hyundai/Kia had self driving systems in development for the past, what, 5 years? Kia debuted its DriveWise in 2016. So they don't start from scratch.
14.
by senozhatsky 7y ago
I pretend that '-s' stands for "source", not "symbolic"; and source file follows -s(ource) option. IOW `ln -s A B' is `link source A to B'.
15.
by senozhatsky 7y ago
Somehow reminds me of this conversation [0]: > Al Viro asked if there is a plan to allow mounting hand-crafted XFS or ext4 > filesystem images. That is an easy way for an attacker to run their own code > in ring 0, he said.
16.
by senozhatsky 7y ago
From the article - "No other agent had served Moscow for so well or so long." That's very questionable. No one knows who the greatest spy was/is.
17.
by senozhatsky 7y ago
Yeah. OOM-kill handling wants to be a silver bullet, sort of. For instance, Linux kernel provides a number of I/O schedulers or net schedulers, etc. to pick from, but OOM kill is "one size fits all". And it doesn't reall
18.
by senozhatsky 7y ago
lkml.org has been unstable for the past few... umm years, so The Linux Foundation runs its own lkml archive - lore.kernel.org/lkml/ Alternative link, just in case: https://lore.kernel.org/lkml/d9802b6a-949b-b3
19.
by senozhatsky 7y ago
Maybe. But I can count something like 6 or 7 buildings on that pic which look glassy to me. I'd say there are several glassy (which reflect sky and water) buildings there [1][2]. [1] https://www.shutterstock.com/video&#
20.
by senozhatsky 7y ago
I like glassy buildings. Can stare at them for minutes; the article makes little sense to me. E.g. Hong Kong Harbour skyline, which is quite "glassy". Many people travel to take a look at it. [1] https://www.tripsavvy.c
21.
by senozhatsky 7y ago
Slightly off topic. Can't help it, but the motif for pain (introduced @ 9:37) sounds to me like, I don't know, Windows (?) error/warning sound. Is it just me?
22.
by senozhatsky 7y ago
> There is one thing I can't understand from the article: it says a low birth rate as a reason of an increase in migration. Why would a low birth rate lead to more migration? Good question. My understanding is that (from the article
23.
by senozhatsky 8y ago
A very cool domain name, by the way.
24.
by senozhatsky 8y ago
> That is indeed very surprising. I think the fact that Go isn't dead-slow can be attributed mainly to the sheer speed of CPUs. Well, I suspect that in any reasonably complex C/C++ application (e.g. firefox) compilers do pass p
25.
by senozhatsky 8y ago
> This is very surprising for a language that targets somewhat high performance. > Looks like it's a 5-10% performance hit, but makes it easier to provide good backtrace information Very interesting indeed. Well, forcing your com
26.
by senozhatsky 8y ago
That "WE MADE HISTORY" at the end definitely should be "WE REPEATED HISTORY".
27.
by senozhatsky 8y ago
Indeed. I also recall a number of pretty cool Max Payne Matrix mods.
28.
by senozhatsky 8y ago
I had a similar thought - profile guided optimizations (PGO).
29.
by senozhatsky 8y ago
> That's not `\n`. That's how acme displays long lines. Oh, yes, sure. I just didn't know how to show the line break, so just "embedded" \n-s. I realize that there are no \n-s there.
30.
by senozhatsky 8y ago
Pretty interesting, that mail utility didn't bother to wrap the words correctly. Notice .. BSD and o\nther .. .. persons i\nn .. .. give a\nn .. and so on.

More ›