Hacker News: senozhatsky

New comment by senozhatsky in "My Favorite C++ Pattern: X Macros (2023)"

senozhatsky — Wed, 26 Mar 2025 03:00:05 +0000

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(
          __array( char, comm, TASK_COMM_LEN )
          __field( pid_t, pid   )
          __field( int, prio   )
          __field( int, target_cpu  )
     ),
    
     TP_fast_assign(
          memcpy(__entry->comm, p->comm, TASK_COMM_LEN);
          __entry->pid  = p->pid;
          __entry->prio  = p->prio; /* XXX SCHED_DEADLINE */
          __entry->target_cpu = task_cpu(p);
     ),
    
     TP_printk("comm=%s pid=%d prio=%d target_cpu=%03d",
          __entry->comm, __entry->pid, __entry->prio,
          __entry->target_cpu)
    );

[1] https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds...

New comment by senozhatsky in "uBlock Origin is no longer available on Chrome web store"

senozhatsky — Mon, 16 Sep 2024 13:41:24 +0000

I wish they offered a paid version of the browser that would have ublock enabled.

New comment by senozhatsky in "Turbo Pascal Turns 40"

senozhatsky — Sun, 03 Dec 2023 05:52:24 +0000

> 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?

Microsoft Was Betting on Unix

senozhatsky — Mon, 27 Jun 2022 10:44:05 +0000

Article URL: https://twitter.com/unix_byte/status/1541202858518843392

Comments URL: https://news.ycombinator.com/item?id=31892729

Points: 1

# Comments: 2

New comment by senozhatsky in "The new Clang _ExtInt feature provides exact bitwidth integer types"

senozhatsky — Thu, 23 Apr 2020 01:37:24 +0000

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

New comment by senozhatsky in "Let's Destroy C"

senozhatsky — Thu, 30 Jan 2020 10:26:31 +0000

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 are vulnerable to "unintended read()-s".

New comment by senozhatsky in "Let's Destroy C"

senozhatsky — Thu, 30 Jan 2020 09:38:45 +0000

Looks even better!

New comment by senozhatsky in "Let's Destroy C"

senozhatsky — Thu, 30 Jan 2020 09:37:40 +0000

Good point. I suppose that you are talking about overwriting terminating NUL, do I get it right? puts() is vulnurable in exactly same way.

New comment by senozhatsky in "Let's Destroy C"

senozhatsky — Thu, 30 Jan 2020 09:25:25 +0000

> 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?

New comment by senozhatsky in "Let's Destroy C"

senozhatsky — Thu, 30 Jan 2020 09:18:51 +0000

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?

New comment by senozhatsky in "Let's Destroy C"

senozhatsky — Thu, 30 Jan 2020 08:55:35 +0000

Could be. But wouldn't then displayln() require the same string placeholder? Be it "%s", or "{1}" or someting else.

New comment by senozhatsky in "Let's Destroy C"

senozhatsky — Thu, 30 Jan 2020 08:49:07 +0000

   > 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 something like

    printf("%s,%s%c\n", "Hello", "World", '!');

and claim that C is awful and that

    displayln("Hello, World!");

is so much better.

New comment by senozhatsky in "Hyundai Motor Group, Aptiv to set up $4B self-driving car venture"

senozhatsky — Tue, 24 Sep 2019 02:29:50 +0000

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.

New comment by senozhatsky in "Everything I googled in a week as a professional software engineer"

senozhatsky — Sat, 07 Sep 2019 12:49:54 +0000

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'.

New comment by senozhatsky in "On-disk format robustness requirements for new filesystems"

senozhatsky — Tue, 20 Aug 2019 07:57:11 +0000

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. The filesystems are not written to expect that kind of
  > (ab)use. When asked if it really was that easy to crash the kernel with a
  > hand-crafted filesystem image, Viro said: "is water wet?"

[0] https://lwn.net/Articles/718639/

New comment by senozhatsky in "Richard Sorge: The Soviet Union’s Master Spy"

senozhatsky — Mon, 19 Aug 2019 05:10:10 +0000

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.

New comment by senozhatsky in "The Linux kernel's inability to gracefully handle low memory pressure"

senozhatsky — Tue, 06 Aug 2019 02:53:57 +0000

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 really look like things are going to change [1][2][3].

[1] https://lore.kernel.org/lkml/alpine.DEB.2.21.1810221406400.1...

[2] https://lore.kernel.org/lkml/20181024155454.4e63191fbfaa0441...

[3] https://lore.kernel.org/lkml/20181023055655.GM18839@dhcp22.s...

New comment by senozhatsky in "The Linux kernel's inability to gracefully handle low memory pressure"

senozhatsky — Tue, 06 Aug 2019 01:09:22 +0000

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-b327-c4a6-3dbca48...

New comment by senozhatsky in "The brain avoids looking at glassy skyscrapers"

senozhatsky — Mon, 05 Aug 2019 08:51:53 +0000

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/clip-7263112-panning-time...

[2] https://www.shutterstock.com/video/clip-27791884-victoria-ha...

Edit: added more links.

New comment by senozhatsky in "The brain avoids looking at glassy skyscrapers"

senozhatsky — Mon, 05 Aug 2019 06:47:54 +0000

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.com/thmb/SPLQhcPHF_u06LNEFd1qIc4p_3Q=/...