/g/ - syscall of the day: rt_sigpending - Technology

Anonymous

syscall of the day: rt_sigpend(...) 03/29/26(Sun)10:37:24 No.108479107

File: pensive.png (161 KB, 512x512)

syscall of the day: rt_sigpending Anonymous 03/29/26(Sun)10:37:24 No.108479107 Archived

previous: >>108473059
#define __NR_rt_sigpending        127
https://man7.org/linux/man-pages/man2/sigpending.2.html

tl;dr:
check your pending signals

first in a series of syscalls involving signaling
or do you say signalling? i think probably signaling looks better, but i am of two minds on the matter...
signals are another interesting but complicated linux kernel topic. it's quite interesting the system they have set up to temporarily block signals (oftentimes done while in the middle of processing an uninterruptible operation). managing the state must be a nightmare....
do we have any opinions on the matter?

relevant resources:
man man
man syscalls
https://man7.org/linux/man-pages/
https://linux.die.net/man/
https://elixir.bootlin.com/linux/
https://elixir.bootlin.com/musl/
https://elixir.bootlin.com/glibc/

Anonymous
03/29/26(Sun)10:49:27 No.108479177

Anonymous 03/29/26(Sun)10:49:27 No.108479177

can we just dispense with the pretense that any of us actually come to this decrepit website to engage with anything on good faith? just skip to the part where some fucktard posts about rule 34 of this mascot or whatever so the wastoids can post "omg wtf BASED moment???" and then we can move on to the next thread where we pretend to be on topic for 2 - 3 posts before we derail it

Anonymous
03/29/26(Sun)10:52:04 No.108479191

Anonymous 03/29/26(Sun)10:52:04 No.108479191

>>108479107
kill yourself

Anonymous
03/29/26(Sun)10:55:27 No.108479209

Anonymous 03/29/26(Sun)10:55:27 No.108479209

>>108479191
why are you being mean this is an effort post

Anonymous
03/29/26(Sun)11:28:39 No.108479425

Anonymous 03/29/26(Sun)11:28:39 No.108479425

File: 1774151291306995.jpg (22 KB, 342x400)

22 KB JPG

WHAT IS A SYSCALL?

Anonymous
03/29/26(Sun)11:29:26 No.108479433

Anonymous 03/29/26(Sun)11:29:26 No.108479433

>>108479107
signals are cursed and need to die

Anonymous
03/29/26(Sun)12:27:42 No.108479801

Anonymous 03/29/26(Sun)12:27:42 No.108479801

File: COCK CHECK.jpg (43 KB, 500x481)

43 KB JPG

thank you Anubis

Anonymous
03/29/26(Sun)14:35:50 No.108480505

Anonymous 03/29/26(Sun)14:35:50 No.108480505

I've really grown to like epoll based programs (even though it is badly documented for some edgecases). If you try it, consider using signalfd as a convenient IPC mechanism in some cases in your eventloop. Beats eventfds for many tasks, especially if you don't have clean parent/ child relationships

Anonymous
03/29/26(Sun)20:07:33 No.108482377

Anonymous 03/29/26(Sun)20:07:33 No.108482377

>>108479107
based OP

Did you know the linux kernel has it's own c library?
i didn't.

Anonymous
03/29/26(Sun)20:08:38 No.108482386

Anonymous 03/29/26(Sun)20:08:38 No.108482386

>>108482377
It does, and it sucks since it hardly implements anything. Doesn't do anything for networking.

Anonymous
03/29/26(Sun)20:10:31 No.108482392

Anonymous 03/29/26(Sun)20:10:31 No.108482392

File: 2026-03-29_20-10.png (54 KB, 441x839)

54 KB PNG

>>108482386
it is not very exhaustive.

Anonymous
03/29/26(Sun)23:09:27 No.108483104

Anonymous 03/29/26(Sun)23:09:27 No.108483104

>>108479425
A miserable little pile of primitives

Anonymous
03/30/26(Mon)01:13:04 No.108483620

Anonymous 03/30/26(Mon)01:13:04 No.108483620

>>108482392
the way the linux kernel uses macros to skinwalk classes in C is fucking horrifying. not sure if you've ever looked into it

Anonymous
03/30/26(Mon)01:29:36 No.108483679

Anonymous 03/30/26(Mon)01:29:36 No.108483679

>>108483620
I haven't seen what kernel devs do yet, but I always thought mimicking class behavior with macros in c was kind of pretty in a messy sort of way.

Anonymous
03/30/26(Mon)04:03:09 No.108484262

Anonymous 03/30/26(Mon)04:03:09 No.108484262

how do you call syscalls right inside the kernel

Anonymous
03/30/26(Mon)04:08:50 No.108484281

Anonymous 03/30/26(Mon)04:08:50 No.108484281

>>108484262
Syscalls are user space code. They don't exist in kernel space.

Anonymous
03/30/26(Mon)04:10:44 No.108484289

Anonymous 03/30/26(Mon)04:10:44 No.108484289

>>108484281
I saw some are able to call them though

Anonymous
03/30/26(Mon)04:11:07 No.108484294

Anonymous 03/30/26(Mon)04:11:07 No.108484294

>>108483620
>le sepples is le bad
>reinvent c++79 poorly with hacky macros
every time

Anonymous
03/30/26(Mon)05:22:06 No.108484547

Anonymous 03/30/26(Mon)05:22:06 No.108484547

File: 1559411583215.jpg (623 KB, 1920x1080)

623 KB JPG

>>108479107
It's been a hot minute since I've seen a syscall in this series that made me go
>what the fuck is this
>how the fuck do you even get in this state
Then I saw
>rt_
and realized nobody uses this anyway

Anonymous
03/30/26(Mon)05:35:12 No.108484609

Anonymous 03/30/26(Mon)05:35:12 No.108484609

>>108484547
Embedded uses it ( ._.)

Anonymous
03/30/26(Mon)08:31:35 No.108485348

Anonymous 03/30/26(Mon)08:31:35 No.108485348

>>108484262
>>108484281
this is sort of misleading
all of the code and symbols for syscalls are exposed by the kernel and are perfectly able to be called by the kernel like any other function. it just also exposes an API to userspace which allows the userspace to request that the kernel perform a syscall on the userspace's behalf

s0ychan
03/30/26(Mon)08:35:30 No.108485360

s0ychan 03/30/26(Mon)08:35:30 No.108485360

>>108479107
Anubussy <3

Anonymous
03/30/26(Mon)08:40:02 No.108485380

Anonymous 03/30/26(Mon)08:40:02 No.108485380

>>108479107
fuck you for reminding me that i wasn't born a woman and will never be one

Anonymous
03/30/26(Mon)08:52:01 No.108485420

Anonymous 03/30/26(Mon)08:52:01 No.108485420

File: zi70i.gif (1.57 MB, 360x270)

1.57 MB GIF

>>108485380
we have the technology. we can rebuild him (her)