| 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
| ||
|
Date: Sun, 1 Mar 2009 01:49:19 -0800 From: David Brownell <david-b@...bell.net> To: Balaji Rao <balajirrao@...nmoko.org> Cc: linux-kernel@...r.kernel.org, spi-devel-general@...ts.sourceforge.net, Andy Green <andy@...nmoko.com> Subject: Re: [PATCH 0/2] spi: Add support for non-blocking synchronous transfers On Saturday 28 February 2009, Balaji Rao wrote: > > That leaves un-answered the question of what to do when > > the SPI bus is busy performing some other transfer. I > > looked at your [2/2] patch, and saw it ignoring that very > > basic issue ... this new call will just poke at the bus, > > trashing any transfer that was ongoing. > > We use s3c24xx_gpio as the master, which is a very simple gpio based > bitbang. > > Yes, it is with this intention, interrupts are disabled around the > actual bitbang code, so that it completes without being interrupted. > Doesn't this guarantee atomicity ? Atomicity isn't the issue so much as the fact that if the bus is in the middle of some transfer to one device, your patch lets another device trash that transmission. I don't know how many more times I can say that your patches introduce DATA CORRUPTION to the system, but it's surely not many more times. -- 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