On 03/05/2018 15:34, Richard Genoud wrote: > On 03/05/2018 14:44, Sebastian Andrzej Siewior wrote: >> On 2018-05-03 14:36:03 [+0200], Richard Genoud wrote: >>> Could resend your patch with Fixes: in the commit message ? >> >> will do shortly. >> >>> BTW, I didn't manage to reproduce the behavior you describe, could you >>> give me your .config and describe a little more how you manage to >>> trigger this bug ? >> .config sent offlist. >> Did you not reproduce this even with the second/debug patch I've sent? > Nope. (I tried on a sam9g35 with buildroot/busybox) > > I have a sama5d3 with a debian as a home server, I'll give it a try. Ok, I reproduced the use-after-free on a SAMA5D2 and on a SAMA5D3, both with debian (sid / stretch). After the patch, no mode funny things in /proc/interrupts. > >> >>> (do you use the console on serial debug ? which board ? ) >> up to date debian sid booting with systemd. After boot completed I do >> "cat /proc/interrupts" and check for the "gone" string. >> This is >> [ 0.000000] OF: fdt:Machine model: SAMA5D3 Xplained >> [ 0.000000] Kernel command line: earlyprintk=ttyS0,115200 console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait >> [ 0.520000] AT91: Detected SoC family: sama5d3 >> [ 0.520000] AT91: Detected SoC: sama5d36, revision 2 >> >> at91-sama5d3_xplained.dtb >> >> Is this enough? > > Great, > > Thanks ! > -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
