Date: Mon, 16 Sep 2024 23:19:18 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 281524] msdosfs error over USB causes a kernel panic Message-ID: <bug-281524-3630-vOW4PAjfjX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-281524-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-281524-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281524 --- Comment #3 from Tomasz "CeDeROM" CEDRO <tomek@cedro.info> --- Thanks Carl, good to hear a temporary solution was found :-) The problem is still here, and FreeBSD should handle it gracefully, so the = fix is needed :-) I would also suggest reporting an issue on CP GitHub - as you have the devi= ce you have the details to fill in the report - you can point the problem is somewhere around Win95 extended attributes. https://github.com/adafruit/circuitpython/issues Someone with a JTAG/SWD debug probe attached to the rPI with CP running and mounted on FreeBSD should catch the problem in the CP firmware. I don't have that board sorry but I guess out of bounds memory write happens causing boa= rd panic and then BSD host panic. This is interesting to verify BSD msdosfs / = fs driver cannot be manipulated by forged FAT device. One more question - just to eliminate some "background writes" - no problem occurred in terminal with no Xorg or you were working on the Xorg desktop? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-281524-3630-vOW4PAjfjX>