| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <871wmom6sb.fsf@javad.com> Date: Mon, 25 Dec 2006 16:41:56 +0300 From: Sergei Organov <osv@...ad.com> To: Jiri Slaby <jirislaby@...il.com> Cc: Andrew Morton <akpm@...l.org>, <linux-kernel@...r.kernel.org> Subject: Re: moxa serial driver testing Jiri Slaby <jirislaby@...il.com> writes: > osv@...ad.com wrote: >> Hi Jiri, >> >> I've figured out that both old and new mxser drivers have two similar >> problems: >> >> 1. When there are data coming to a port, sometimes opening of the port >> entirely locks the box. This is quite reproducible. Any idea what's >> wrong and how can I help to debug it? > > Could you test the patch below, if something changes? Something did change. Now it becomes rather difficult to get the box to hang, though not impossible. Another thing that changed is that now I can see [parts of] oopses on screen. I've got two pictures of the screen with different oopses. If you need them, let me know and I'll send them to you in a separate mail not to pollute lkml with JPEGs. One of these oopses happened on kernel with lock debugging enabled, but I can't see anything relevant in dmesg log after resetting the box. SysRq magic still doesn't work after hang. As for the problem with module unloading when port is open, your another patch does fix it indeed. -- Sergei. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists