Fosstodon

N-gated Hacker News🚨 Breaking News: <a href="https://mastodon.social/tags/Developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Developers</a> unveil groundbreaking strategy to deal with skeptics of io_uring: just ignore them! 🙉 Because who needs <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> when you have beautiful, error-free code, right? After all, <a href="https://mastodon.social/tags/vulnerabilities" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulnerabilities</a> are just misunderstood features waiting to be automated away! 🤖✨ <a href="https://github.com/axboe/liburing/discussions/1047" rel="nofollow noopener" translate="no" target="_blank">https://github.com/axboe/liburing/discussions/1047</a> <a href="https://mastodon.social/tags/BreakingNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#BreakingNews</a> <a href="https://mastodon.social/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a> <a href="https://mastodon.social/tags/Automation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Automation</a> <a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/ngated" class="mention hashtag" rel="nofollow noopener" target="_blank">#ngated</a>

Hacker NewsHow to handle people dismissing io_uring as insecure?<a href="https://github.com/axboe/liburing/discussions/1047" rel="nofollow noopener" translate="no" target="_blank">https://github.com/axboe/liburing/discussions/1047</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a> <a href="https://mastodon.social/tags/secure" class="mention hashtag" rel="nofollow noopener" target="_blank">#secure</a> <a href="https://mastodon.social/tags/dismissals" class="mention hashtag" rel="nofollow noopener" target="_blank">#dismissals</a> <a href="https://mastodon.social/tags/handling" class="mention hashtag" rel="nofollow noopener" target="_blank">#handling</a> <a href="https://mastodon.social/tags/discussions" class="mention hashtag" rel="nofollow noopener" target="_blank">#discussions</a> <a href="https://mastodon.social/tags/technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#technology</a>

N-gated Hacker News🐢 Ah, the classic story of "let's reinvent the wheel, but with extra steps"! 🚀 Instead of using ls like mere mortals, let's sprinkle some <a href="https://mastodon.social/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a> magic dust on it and call it a day. Because clearly, what the world needed was a multi-pipeline, issue-ridden version of listing files! 🙃 <a href="https://tangled.sh/@rockorager.dev/lsr" rel="nofollow noopener" translate="no" target="_blank">https://tangled.sh/@rockorager.dev/lsr</a> <a href="https://mastodon.social/tags/reinventingthewheel" class="mention hashtag" rel="nofollow noopener" target="_blank">#reinventingthewheel</a> <a href="https://mastodon.social/tags/filesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#filesystem</a> <a href="https://mastodon.social/tags/innovation" class="mention hashtag" rel="nofollow noopener" target="_blank">#innovation</a> <a href="https://mastodon.social/tags/techhumor" class="mention hashtag" rel="nofollow noopener" target="_blank">#techhumor</a> <a href="https://mastodon.social/tags/programmingstruggles" class="mention hashtag" rel="nofollow noopener" target="_blank">#programmingstruggles</a> <a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/ngated" class="mention hashtag" rel="nofollow noopener" target="_blank">#ngated</a>

Hacker Newslsr: ls with io_uring<a href="https://tangled.sh/@rockorager.dev/lsr" rel="nofollow noopener" translate="no" target="_blank">https://tangled.sh/@rockorager.dev/lsr</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/lsr" class="mention hashtag" rel="nofollow noopener" target="_blank">#lsr</a> <a href="https://mastodon.social/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a> <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/ls" class="mention hashtag" rel="nofollow noopener" target="_blank">#ls</a> <a href="https://mastodon.social/tags/performance" class="mention hashtag" rel="nofollow noopener" target="_blank">#performance</a> <a href="https://mastodon.social/tags/optimization" class="mention hashtag" rel="nofollow noopener" target="_blank">#optimization</a>

Nils Goroll 🕊️:varnishcache:With the merge of <a href="https://github.com/varnishcache/varnish-cache/pull/4209" target="_blank" rel="nofollow noopener" translate="no">https://github.com/varnishcache/varnish-cache/pull/4209</a> <a href="https://fosstodon.org/tags/VarnishCache" class="mention hashtag" rel="tag">#VarnishCache</a> is now prepared for using asynchronous I/O also on the network side.Stay tuned. <a href="https://fosstodon.org/tags/io_uring" class="mention hashtag" rel="tag">#io_uring</a>

Andrés GómezMy <a href="https://floss.social/@igalia" class="u-url mention" rel="nofollow noopener" target="_blank">@igalia</a> colleague Luís Henriques has just published a very interesting post about the work he has been doing lately in the Linux <a href="https://hostux.social/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> about <a href="https://hostux.social/tags/FUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#FUSE</a> over <a href="https://hostux.social/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a>.<a href="https://luis.camandro.org/2025-06-14-fuse-over-io_uring.html" rel="nofollow noopener" translate="no" target="_blank">https://luis.camandro.org/2025-06-14-fuse-over-io_uring.html</a>

Kunai Project🚀 New Blog Post: Kunai vs io_uring (<a href="https://why.kunai.rocks/blog/kunai-vs-io_uring" rel="nofollow noopener" translate="no" target="_blank">https://why.kunai.rocks/blog/kunai-vs-io_uring</a>) 🚀💡 Ever wondered how io_uring revolutionizes I/O operations in the Linux kernel? Inspired by Armo's blog post (<a href="https://www.armosec.io/blog/io_uring-rootkit-bypasses-linux-security/" rel="nofollow noopener" translate="no" target="_blank">https://www.armosec.io/blog/io_uring-rootkit-bypasses-linux-security/</a>) about a PoC rootkit using io_uring, we explored this feature's security implications and how tools like Kunai can monitor these operations.🔍 Key Takeaways: 🔹 io_uring boosts I/O performance by reducing system call overhead and enabling asynchronous operations 🔹 Security tools struggle to monitor io_uring due to its unique handling of operations 🔹 Kunai now provides visibility into io_uring operations, though blocking malicious activities remains challenging 🔹 Recent kernel versions have introduced auditing and security controls for io_uring, but these are still limited📖 Read more: <a href="https://why.kunai.rocks/blog/kunai-vs-io_uring" rel="nofollow noopener" translate="no" target="_blank">https://why.kunai.rocks/blog/kunai-vs-io_uring</a><a href="https://infosec.exchange/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://infosec.exchange/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a> <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://infosec.exchange/tags/ThreatDetection" class="mention hashtag" rel="nofollow noopener" target="_blank">#ThreatDetection</a> <a href="https://infosec.exchange/tags/SOC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SOC</a> <a href="https://infosec.exchange/tags/DFIR" class="mention hashtag" rel="nofollow noopener" target="_blank">#DFIR</a>

Marcel WaldvogelAll you never wanted to know about creating fast socket I/O on <a href="https://waldvogel.family/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a>. Unless you are a real geek.A small, ultra-high performance publish-subscribe server doing kind of TCP <a href="https://waldvogel.family/tags/multicast" class="mention hashtag" rel="nofollow noopener" target="_blank">#multicast</a> using <a href="https://waldvogel.family/tags/sendfile" class="mention hashtag" rel="nofollow noopener" target="_blank">#sendfile</a>, <a href="https://waldvogel.family/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a>, <a href="https://waldvogel.family/tags/splice" class="mention hashtag" rel="nofollow noopener" target="_blank">#splice</a>, (mapped) files, and <a href="https://waldvogel.family/tags/fallocate" class="mention hashtag" rel="nofollow noopener" target="_blank">#fallocate</a> for file hole punching.Saturating a 10 Gbps link with useful data with just 8 cores.A beautiful writeup for anyone into fast Linux networking. Not just for <a href="https://waldvogel.family/tags/ATproto" class="mention hashtag" rel="nofollow noopener" target="_blank">#ATproto</a> h/t <a href="https://smnn.ch/@nohillside" class="u-url mention" rel="nofollow noopener" target="_blank">@nohillside</a> <a href="https://waldvogel.family/tags/PubSub" class="mention hashtag" rel="nofollow noopener" target="_blank">#PubSub</a> <a href="https://waldvogel.family/tags/Kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kernel</a> <a href="https://waldvogel.family/tags/Hacking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hacking</a> <a href="https://www.asayers.com/jetrelay" rel="nofollow noopener" translate="no" target="_blank">https://www.asayers.com/jetrelay</a>

Gea-Suan Lin<a href="https://blog.gslin.org/archives/2025/05/08/12389/postgresql-18-%e7%9a%84-async-i-o/" rel="nofollow noopener" translate="no" target="_blank">https://blog.gslin.org/archives/2025/05/08/12389/postgresql-18-%e7%9a%84-async-i-o/</a>PostgreSQL 18 的 async i/o<a href="https://abpe.org/tags/async" class="mention hashtag" rel="nofollow noopener" target="_blank">#async</a> <a href="https://abpe.org/tags/database" class="mention hashtag" rel="nofollow noopener" target="_blank">#database</a> <a href="https://abpe.org/tags/i" class="mention hashtag" rel="nofollow noopener" target="_blank">#i</a>/o <a href="https://abpe.org/tags/input" class="mention hashtag" rel="nofollow noopener" target="_blank">#input</a> <a href="https://abpe.org/tags/io" class="mention hashtag" rel="nofollow noopener" target="_blank">#io</a> <a href="https://abpe.org/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a> <a href="https://abpe.org/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://abpe.org/tags/oltp" class="mention hashtag" rel="nofollow noopener" target="_blank">#oltp</a> <a href="https://abpe.org/tags/output" class="mention hashtag" rel="nofollow noopener" target="_blank">#output</a> <a href="https://abpe.org/tags/performance" class="mention hashtag" rel="nofollow noopener" target="_blank">#performance</a> <a href="https://abpe.org/tags/pg" class="mention hashtag" rel="nofollow noopener" target="_blank">#pg</a> <a href="https://abpe.org/tags/pgsql" class="mention hashtag" rel="nofollow noopener" target="_blank">#pgsql</a> <a href="https://abpe.org/tags/postgresql" class="mention hashtag" rel="nofollow noopener" target="_blank">#postgresql</a> <a href="https://abpe.org/tags/rdbms" class="mention hashtag" rel="nofollow noopener" target="_blank">#rdbms</a> <a href="https://abpe.org/tags/read" class="mention hashtag" rel="nofollow noopener" target="_blank">#read</a> <a href="https://abpe.org/tags/speed" class="mention hashtag" rel="nofollow noopener" target="_blank">#speed</a> <a href="https://abpe.org/tags/stream" class="mention hashtag" rel="nofollow noopener" target="_blank">#stream</a>

GeeklandRootkits invisibles: el nuevo desafío para las herramientas de seguridad en Linux <a href="https://mastodon.social/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a> <a href="https://mastodon.social/tags/seguridad" class="mention hashtag" rel="nofollow noopener" target="_blank">#seguridad</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://blog.desdelinux.net/rootkits-invisibles-el-nuevo-desafio-para-las-herramientas-de-seguridad-en-linux/" rel="nofollow noopener" translate="no" target="_blank">https://blog.desdelinux.net/rootkits-invisibles-el-nuevo-desafio-para-las-herramientas-de-seguridad-en-linux/</a>

Scripter :verified_flashing:Linux: Kritische Sicherheitslücke in Kernel-API entdeckt <a href="https://winfuture.de/news,150557.html" rel="nofollow noopener" translate="no" target="_blank">https://winfuture.de/news,150557.html</a> <a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://social.tchncs.de/tags/LinuxKernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#LinuxKernel</a> <a href="https://social.tchncs.de/tags/Sicherheitsl%C3%BCcke" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sicherheitslücke</a> <a href="https://social.tchncs.de/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a>

argv minus oneDo any operating systems other than <a href="https://mastodon.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> (<a href="https://mastodon.sdf.org/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a>, <a href="https://mastodon.sdf.org/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a>, <a href="https://mastodon.sdf.org/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a>, <a href="https://mastodon.sdf.org/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenBSD</a>, etc) have an API for non-blocking file IO?I know Linux has that in <a href="https://mastodon.sdf.org/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a>, which can do almost any IO operation (even fsync) in the background and tell you when it's done, but is that the only OS with such a feature?<a href="https://mastodon.sdf.org/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://mastodon.sdf.org/tags/async" class="mention hashtag" rel="nofollow noopener" target="_blank">#async</a>

Nils Goroll 🕊️:varnishcache:Does anyone happen to have any information on the relevance of UIO_FASTIOV (defined as 8 on <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="tag">#Linux</a>). I understand that submitting vectored io with within this limit can avoid dynamic memory allocation in the kernel, but is this relevant in any way in practice? Is it relevant with <a href="https://fosstodon.org/tags/io_uring" class="mention hashtag" rel="tag">#io_uring</a> ?

Thorsten Leemhuis (acct. 1/4)Support for <a href="https://fosstodon.org/tags/io_uring" class="mention hashtag" rel="tag">#io_uring</a> communication between <a href="https://fosstodon.org/tags/kernel" class="mention hashtag" rel="tag">#kernel</a> and [<a href="https://fosstodon.org/tags/fuse" class="mention hashtag" rel="tag">#fuse</a>] userspace using IORING_OP_URING_CMD is the highlight from the main fuse (Filesystem in Userspace) updates merged for <a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="tag">#Linux</a> 6.14:<a href="https://git.kernel.org/torvalds/c/92cc9acff7194b1b9db078901f2a83182bb73202" target="_blank" rel="nofollow noopener" translate="no">https://git.kernel.org/torvalds/c/92cc9acff7194b1b9db078901f2a83182bb73202</a>Miklos furthermore writes:'"Following features enable gains in performance compared to the regular interface:- Allow processing multiple requests with less syscall overhead- Combine commit of old and fetch of new fuse request- CPU/NUMA affinity of queues"'<a href="https://fosstodon.org/tags/LinuxKernel" class="mention hashtag" rel="tag">#LinuxKernel</a>

Felix MoessbauerJust watching the <a href="https://mastodon.social/tags/38c3" class="mention hashtag" rel="nofollow noopener" target="_blank">#38c3</a> <a href="https://mastodon.social/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a> talk. That's the <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> subsystem I recently fixed bugs around incorrect <a href="https://mastodon.social/tags/CPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#CPU</a> affinities. <a href="https://events.ccc.de/congress/2024/hub/en/event/iouring-ebpf-xdp-and-afxdp/" rel="nofollow noopener" translate="no" target="_blank">https://events.ccc.de/congress/2024/hub/en/event/iouring-ebpf-xdp-and-afxdp/</a>

Nils Goroll 🕊️:varnishcache:as i am currently working on making <a href="https://fosstodon.org/tags/varnishcache" class="mention hashtag" rel="tag">#varnishcache</a> client side io <a href="https://fosstodon.org/tags/async" class="mention hashtag" rel="tag">#async</a>'hronous with <a href="https://fosstodon.org/tags/io_uring" class="mention hashtag" rel="tag">#io_uring</a>, i must say that <a href="https://lucumr.pocoo.org/2024/11/18/threads-beat-async-await/" target="_blank" rel="nofollow noopener" translate="no">https://lucumr.pocoo.org/2024/11/18/threads-beat-async-await/</a> made me think if we need more facilities for forensic analysis…

amackifThis is probably a ridiculous question: is <a href="https://mastodon.social/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a> an event loop or does it resemble one? And is it possible to make all <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.social/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#kernel</a> subsystems use it? E.g. GPU driversIf so, would it be possible to write something like a <a href="https://mastodon.social/tags/microkernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#microkernel</a> with good performance where internally subsystems submit things to <a href="https://mastodon.social/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a>?

Nils Goroll 🕊️:varnishcache:using <a href="https://fosstodon.org/tags/io_uring" class="mention hashtag" rel="tag">#io_uring</a> for storage in <a href="https://fosstodon.org/tags/varnishcache" class="mention hashtag" rel="tag">#varnishcache</a> <a href="https://fosstodon.org/tags/allsystemsgo" class="mention hashtag" rel="tag">#allsystemsgo</a> <a href="https://fosstodon.org/tags/ASG2024" class="mention hashtag" rel="tag">#ASG2024</a> <a href="https://media.ccc.de/v/all-systems-go-2024-305-using-iouring-for-storage" target="_blank" rel="nofollow noopener" translate="no">https://media.ccc.de/v/all-systems-go-2024-305-using-iouring-for-storage</a>From: <a href="https://botsin.space/@mediacccde" class="u-url mention">@mediacccde</a> <a href="https://botsin.space/@mediacccde/113203506819669014" target="_blank" rel="nofollow noopener" translate="no">https://botsin.space/@mediacccde/113203506819669014</a>

kikA new way to perform syscalls in the linux kernel, both batched and asynchronous : <a href="https://matklad.github.io/2024/09/32/-what-is-io-uring.html" rel="nofollow noopener" translate="no" target="_blank">https://matklad.github.io/2024/09/32/-what-is-io-uring.html</a>There is something I don't understand though : if it's a ringbuffer, it means that some syscalls get discarded if the buffer gets full? 🤔 Or maybe it refuses more calls then, but then why make it a ringbuffer rather than a classic FIFO?<a href="https://dice.camp/tags/io_uring" class="mention hashtag" rel="nofollow noopener" target="_blank">#io_uring</a> <a href="https://dice.camp/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> (also, why is this article timestamp in the future, on Oct 2, 2024? ^^ )

Luke T. ShumakerAnyone familiar with <a href="https://fosstodon.org/tags/io_uring" class="mention hashtag" rel="tag">#io_uring</a> have any idea what this bit in mini_liburing.h is doing? I think I understand the rest of io_uring_submit(), but I can't fathom what this bit is doing. if (*sq->khead != *sq->ktail) { submitted = *sq->kring_entries; goto submit; }(Also, isn't the IORING_ENTER_GETEVENTS flag at the end no-op, since min_complete=0 ?)

Recent searches

Search options

Administered by:

Server stats:

#io_uring