(Resend as LKML didn't take outlook settings.) > On Fri, 2019-05-31 at 11:27 -0700, Dexuan-Linux Cui wrote: > > Hi, > > Did you know about the panic reported here: > > https://marc.info/?t=155930773000003&r=1&w=2 > > > > "Kernel panic - not syncing: stack-protector: Kernel stack is > > corrupted in: write_irq_affinity.isra> " > > > > This panic is reported on PowerPC and x86. > > > > In the case of x86, we see a lot of "get_swap_device: Bad swap file entry" > > errors before the panic: > > > > ... > > [ 24.404693] get_swap_device: Bad swap file entry 5800000000000001 > > [ 24.408702] get_swap_device: Bad swap file entry 5c00000000000001 > > [ 24.412510] get_swap_device: Bad swap file entry 6000000000000001 > > [ 24.416519] get_swap_device: Bad swap file entry 6400000000000001 > > [ 24.420217] get_swap_device: Bad swap file entry 6800000000000001 > > [ 24.423921] get_swap_device: Bad swap file entry 6c00000000000001
[..] I don't have a panic, but I observe many lines like this. > Looks familiar, > > https://lore.kernel.org/lkml/1559242868.6132.35.ca...@lca.pw/ > > I suppose Andrew might be better of reverting the whole series first before > Yury > came up with a right fix, so that other people who is testing linux-next don't > need to waste time for the same problem. I didn't observe any problems with this series on top of 5.1, and there's a fix for swap\ that eliminates the problem on top of current next for me: https://lkml.org/lkml/2019/5/30/1630 Could you please test my series with the patch above? Thanks, Yury
