On Mon, Sep 15, 2025 at 6:58 PM Breno Leitao <lei...@debian.org> wrote: > > On Mon, Sep 15, 2025 at 03:55:53AM -0700, Breno Leitao wrote: > > On Mon, Sep 15, 2025 at 06:50:15PM +0800, Lei Yang wrote: > > > This series of patches introduced a kernel panic bug. The tests are > > > based on the linux-next commit [1]. I tried it a few times and found > > > that if I didn't apply the current patch, the issue wouldn't be > > > triggered. After applying the current patch, the probability of > > > triggering the issue was 3/3. > > > > > > Reproduced steps: > > > 1. git clone > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > > > 2. applied this series of patches > > > 3. compile and install > > > 4. reboot server(A kernel panic occurs at this step) > > > > Thanks for the report. Let me try to reproduce it on my side.
Hi Breno > > > > Is this a physical machine, or, are you using a VM with the virtio change? Yes, I test it with a physical machine. I didn't used VM， just install rpm which compiled based on this series patches, then hit kernel pahic at server rebooting. > > Also, I've just sent v3 earlier today, let me know if you have chance to > test it as well, given it fixes the issue raised by Jakub in [1] > > Link: https://lore.kernel.org/all/20250914125949.17ea0...@kernel.org/ [1] I already submitted a job to test v3, the test will be completed tomorrow and I will update the results promptly. Best Regards Lei >
