| 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: <20131002163418.GA4557@polaris.bitmath.org> Date: Wed, 2 Oct 2013 18:34:18 +0200 From: Henrik Rydberg <rydberg@...omail.se> To: Guenter Roeck <linux@...ck-us.net> Cc: Chris Murphy <bugzilla@...orremedies.com>, Josh Boyer <jwboyer@...oraproject.org>, khali@...ux-fr.org, lm-sensors@...sensors.org, "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org> Subject: Re: applesmc oops in 3.10/3.11 > >>One thing I have seen in all logs is the earlier "send_byte fail" message, so > >>I think that is a pre-requisite. > > > >Not necessarily - it could be that the patch actually fixes the root > >cause. One possible scenario is that on recent SMCs, some of the > >commands produce more data than we actually read. This would > >eventually lead to both data corruption and overflow somwhere in the > >SMC internals. If the original SMC error is interpreted as a read > >buffer overflow, then that problem should be fixed with this patch. > > > > Good point. > > But shouldn't we at least get the "flushed %d bytes" warning message in this case ? The explanation I have there is that the (newer) SMC needs the application to read the 'no more bytes' or it will get confused. It makes sense, if the number of bytes to read is no longer specified. Thanks, Henrik -- 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