Open Source Summit Korea 2026

The Linux desktop system boasts strong customization and freedom, but its application ecosystem has long been a weakness. Recently, the Android system has millions of applications, covering all aspects of work and life. If we could integrate these and create a brand-new desktop experience, what kind of impact would it have?

This presentation will introduce our open-source project - OpenFDE (Open Fusion Desktop Environment). This is an innovative desktop environment that integrates the Android open-source project (AOSP) deeply with Linux applications, enabling users to run various Android applications seamlessly on their Linux desktops.

We will share:
1、Project Vision: Why did we choose AOSP and Linux integration? What problems are we aiming to solve?
2、Core Architecture: How do we achieve the integration of these two major systems? In-depth analysis of the key technologies of OpenFDE in terms of graphics, window management, and application lifecycle.
3、Live Demonstration: Witness firsthand the smooth coexistence of Linux and the latest Android applications (including large-scale games) in the OpenFDE environment.

In modern cloud environments, CPU usage often looks healthy while applications still experience latency and unpredictable slowdowns. In one Kubernetes based system running latency sensitive workloads, services degraded despite CPU staying below 50%. Traditional monitoring showed no clear issue, leading to delayed debugging and reactive fixes.

This case study highlights how the real bottleneck was hidden in the Linux scheduler specifically run queue contention and scheduling delays. By examining run queue depth and task scheduling behavior, the team uncovered how fairness-driven scheduling (CFS) impacted performance under load. The session also touches on how newer approaches like EEVDF aim to improve scheduling decisions.

The result was faster root cause identification, better workload tuning, and improved application responsiveness without scaling resources.

Key Takeaways:

- Why CPU utilization can mislead performance analysis
- How run queue depth and scheduling latency impact applications
- The gap between fair scheduling and real-world performance
- What’s changing in modern schedulers (CFS > EEVDF)
- Practical ways to reason about scheduler related bottlenecks

Service operators often face a constant friction: maintaining high Service Level Indicators (SLIs) versus addressing immediate security vulnerabilities. While userspace updates cause minimal disruption, mitigating Linux kernel vulnerabilities traditionally mandates a full system reboot, forcing administrators into the dilemma of choosing between proactive security practices and continuous uptime.

This session explores the workings of Linux kernel live patching, details how a livepatch kernel module is built, examines the internal mechanisms that power the technology (e.g., ftrace), and provides a practical overview of the current ecosystem so administrators can start using live patches immediately.

Modern Linux init systems don't just magically start executing services. Long before PID 1 reaches its main loop, a complex, carefully orchestrated dance of initialization routines takes place. This presentation explores the crucial, often-overlooked machinery bridging the compiler toolchain and system orchestration: the linker.

Often treated as a black box, the linker (ld) is an immensely powerful tool for low-level systems engineers. This deep dive pulls back the curtain on how modern init architectures leverage custom linker scripts, specifically defined ELF sections, and compiler directives (like __attribute__((constructor))) to precisely control execution order and optimize memory layouts before the system fully comes alive.

Catching transient performance drops is notoriously hard; by the time you attach a profiler, the bottleneck is often gone. Continuous tracing is the solution, but manually analyzing the resulting massive data is a huge hurdle.

This session introduces a practical methodology for always-on performance monitoring and automated analysis using Guider. First, we demonstrate how Guider efficiently profiles system performance in the background with minimal overhead. Upon detecting an anomaly, it automatically generates a retroactive report using trace data captured just before the event.

We will then show how to feed these structured reports into an AI pipeline. Instead of manually deciphering complex kernel metrics, you will see how AI instantly pinpoints the root cause of performance regressions.

Attendees will learn to build a continuous monitoring pipeline that automatically turns raw trace data into real-time, actionable insights.

In this session, as the newly appointed Executive Director of OpenChain, I will outline the strategic direction for OpenChain in 2027 and beyond. Building on the solid foundation of our existing ISO standards, including ISO 5230:2020 and ISO 18974, I will share the next steps OpenChain will take to expand its global reach. We will focus on fostering international collaboration, adapting to emerging regulatory landscapes, and driving innovation in open-source compliance practices worldwide.

What if you could replace your entire OS userspace — binaries, configs, services, even init itself — without ever stopping the kernel? No firmware POST, no hardware re-init, no multi-minute downtime. Just a clean userspace restart in seconds.

That's what soft-reboot (systemctl soft-reboot), implemented in systemd, delivers: a primitive that tears down all of userspace, pivots into a fresh root filesystem, and re-launches PID 1 — while the running kernel stays untouched.

This talk unpacks how soft-reboot works under the hood, why it matters for modern OS update workflows, and how it compares to a traditional reboot and kexec. We'll walk through real production use cases: zero-downtime OS updates, staged fleet rollouts, and rapid recovery from a wedged userspace — without paying the cost of a full boot cycle.

Attendees will leave with a clear mental model of soft-reboot internals, practical guidance on when to choose it over a full reboot or kexec, and concrete patterns for building soft-reboot-aware update pipelines.

If you've ever wished you could ship an OS update as fast as restarting a service, this talk is for you.