hakurei/internal/uevent/uevent.go, branch developlow-level userspace tooling for Rosa OShttp://src.rosa.moe/hakurei/atom/internal/uevent/uevent.go?h=develop2026-04-06T03:42:47Zinternal/uevent: optionally pass UUID during coldboot2026-04-06T03:42:47ZOphestracat@gensokyo.uk2026-04-06T02:43:16Zurn:sha1:cd0beeaf8ed5fb81ba20375517c7a3bf34fd27cd
This enables rejection of non-coldboot synthetic events.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/uevent: integrate error handling in event loop2026-03-30T15:10:14ZOphestracat@gensokyo.uk2026-03-30T14:49:16Zurn:sha1:91a2d4d6e1c0039f6b442c8c97b1aa809e09e33b
There are many subtleties when recovering from errors in the event loop, and coldboot requires internals to drain the receive buffer as synthetic uevents are being arranged.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/uevent: separate recvmsg helper2026-03-29T17:53:26ZOphestracat@gensokyo.uk2026-03-29T17:53:26Zurn:sha1:b5592633f5b980970808fc5be43b0fb4f4d4e784
This enables messages to be received separately.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/netlink: set receive buffer size2026-03-29T17:14:47ZOphestracat@gensokyo.uk2026-03-29T17:14:47Zurn:sha1:584e30216896fd4de6301f9cf937829e16d22c49
This is done by both systemd sd-device and AOSP ueventd to improve robustness. Rosa OS will still handle ENOBUFS via coldboot but a big buffer should mitigate this as well.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/uevent: handle state divergence2026-03-29T16:50:09ZOphestracat@gensokyo.uk2026-03-29T16:48:20Zurn:sha1:141958656f8a83a4f5703bd4890389dd1f180e0a
This requires the caller to arrange for a coldboot to happen, some time after this error is encountered, and to resume event processing.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/netlink: switch to recvmsg/sendmsg2026-03-29T14:36:00ZOphestracat@gensokyo.uk2026-03-29T14:34:53Zurn:sha1:648079f42cd872f16110e571ce34fdbd90f7c476
These are more flexible than recvfrom/sendto.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/uevent: consume kernel-originated events2026-03-28T06:39:16ZOphestracat@gensokyo.uk2026-03-27T16:06:17Zurn:sha1:ea014d6af2d1481ba05ffed2dddffeed370f6622
These are not possible to cover outside integration vm. Extreme care is required when dealing with this method, so keep it simple.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/uevent: exclusive socket access2026-03-27T16:01:06ZOphestracat@gensokyo.uk2026-03-27T16:01:06Zurn:sha1:1b48484c169daa48a006f52f48766d358fa8f2bc
This is a much simplified mutex, since blocking is not required.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/uevent: nontrivial errors2026-03-27T15:07:56ZOphestracat@gensokyo.uk2026-03-27T15:07:56Zurn:sha1:30f459e690ca561d3932cb6efa0cf14ea53c25b2
These errors are best represented as JSON.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/uevent: recoverable errors2026-03-27T13:58:16ZOphestracat@gensokyo.uk2026-03-27T13:58:16Zurn:sha1:8766fddcb3a8047673e513ce0d60c8c46edb5ba1
This runs in the Rosa OS init, so recover as much as possible, as otherwise it is likely to require a full system reboot to resume event processing. The caller is responsible for reporting the error.
Signed-off-by: Ophestra <cat@gensokyo.uk>