Posts
529Following
99Followers
116- Linux Kernel Developer @ Oracle (Linux Kernel MM) (2025.02 ~ Present)
- Reviewer for the Linux Slab & Reverse Mapping subsystem
- Former Intern @ NVIDIA, SK Hynix, Panmnesia (Security, MM and CXL)
- B.Sc. in Computer Science & Engineering, Chungnam National University (Class of 2025)
Opinions are my own.
My interests are:
Memory Management,
Computer Architecture,
Circuit Design,
Virtualization
Harry (Hyeonggon) Yoo
hyeyoo
1
0
4
Perhaps should have refused a looong nap at night before 2am call
0
0
1
repeated
Omar Sandoval
osandov
0
3
6
Harry (Hyeonggon) Yoo
hyeyooSLAIB?
size = ai_prompt("Size sufficient to fit five integers");
gfp = ai_prompt("Appropriate GFP flags for the current context?");
array = kmalloc(size, gfp);
1
1
1
repeated
Oleksandr Natalenko, MSE 
oleksandr@natalenko.name
linux-stable is a vibe-backported frankenkernel
0
2
1
repeated
Linux Plumbers Conference
linuxplumbersconf@mastodon.socialAll microconferences (MCs) at LPC 2025 have been accepted! It is time to submit topics to your favorite MCs.
Please check out our latest blog post for the list of MCs, and how to create a ideal MC topic.
https://lpc.events/blog/current/index.php/2025/07/25/all-microconferences-have-been-accepted/
0
10
4
repeated
Kees Cook
kees@hachyderm.ioI've been playing with the LLM code assistants, trying to stress them out with the Linux kernel code. So far, I've had success with them writing reasonable unit tests:
https://lore.kernel.org/lkml/20250717085156.work.363-kees@kernel.org/
https://lore.kernel.org/lkml/20250724030233.work.486-kees@kernel.org/
These both saved me some time since it emitted quite a lot of good boundary testing code, but I had to massage them both a bit until I was happy with the coverage. But it was a net win on time spent.
And then I walked it through fixing a buffer overflow. This one didn't save me any time because I had to tell it how to look at the problem. Since it was a shorter/simpler session, I included my exact prompts just for anyone interested in what I did:
https://lore.kernel.org/lkml/20250724080756.work.741-kees@kernel.org/
4
3
3
repeated
Kees Cook
kees@hachyderm.ioThis graph is the one I'm most excited about: the lifetime of security flaws in Linux is finally starting to get shorter (and the number of fixed flaws continues to rise).
https://hachyderm.io/@LinuxSecSummit@social.kernel.org/114750428620118674
1
13
3
Personally I use it to rephrase/proofread text or quickly look something up (as a first resort before grepping through git history or mailing list archive). I heard AUTOSEL uses LLMs to determine whether a patch should be backported to -stable or not.
But at this point, I really hope no one sends any code written or guided by AI to the mailing list. It might be fine to get shallow reviews of human-written code from LLMs, but I doubt they're capable of writing sane kernel code or offering deep reviews.
1
0
1
Harry (Hyeonggon) Yoo
hyeyooMost of the time, PGD entries are populated during the boot process, and new tasks inherit page tables derived from the swapper process, so everything works fine.
However, if you're adding memory at runtime via memory hotplugging and populating new PGD entries for the vmemmap (i.e., the struct page array) and the direct mapping area, you need to iterate over all page tables in the system and update them accordingly to make it visible to all tasks.
Failing to handle this properly can lead to a situation where you think the page tables are set up correctly, but in reality, only init_mm.pgd (page table of the swapper process) was updated, not the page table of current task. This leads to kernel crashes since the PGD entry is not set up properly.
x86 code has mechanisms to handle this kind of synchronization, but it’s easy to be overlooked and introduce kernel crashes as the code evolves. Here’s my patch series that addresses the issue and aims to make it more robust: https://lore.kernel.org/linux-mm/20250709131657.5660-1-harry.yoo@oracle.com/
0
1
7