Re: [PATCH 5/8] fstatat etc.: fix wrong machine code for calls
Paul Eggert <[email protected]>
| Newsgroups | gmane.comp.lib.gnulib.bugs |
|---|---|
| Organization | UCLA Computer Science Department |
| Message-ID | <[email protected]> |
On 2026-06-16 11:43, Bruno Haible wrote: > Paul Eggert wrote: >> ... assume that the calls’ arguments cannot be >> null pointers. This assumption became false with the release of >> Linux kernel 6.11 (2024). > > Wow. I'm impressed that you notice that. Is there a systematic way > for us to notice such changes? Only sort-of-systematic way I can think of offhand is to have LLMs review kernel and libc changes. I found the problem the hard way: some of my experimental code got miscompiled. Luckily I didn't need to spend much time diagnosing: the wrong machine code was a dead giveaway.