| 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, 15 Jan 2012 13:50:30 +0100 From: Jens Axboe <axboe@...nel.dk> To: Christoph Hellwig <hch@...radead.org> CC: Linus Torvalds <torvalds@...ux-foundation.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Sam Bradshaw (sbradshaw)" <sbradshaw@...ron.com> Subject: Re: [GIT PULL] Block drivers for 3.3-rc On 2012-01-15 13:44, Christoph Hellwig wrote: > On Sun, Jan 15, 2012 at 01:22:05PM +0100, Jens Axboe wrote: >> Good point, I had forgotten about the ordered writes, I believe the rest >> of the items have been handled. The driver/hw, as it stands, does not >> reorder writes and it doesn't have a write back cache. So it should >> actually be safe. Any acked write is stable. Sam, correct me if I'm >> wrong. > > I tried to get that out of the micron folks a while ago but don't > remember getting an answer. If that's actually tree please remove > the (misnamed) barrier argument from mtip_hw_submit_io, and maybe add > a comment that the current hardware can't have a volatile write cache. Sure, will do post pull to not mess up the current pull request. > Btw, does the hardware claim to have writeback caches in the ATA > IDENTIFY words related to it? I'll let Sam answer this one and the question above, it's better if it comes from the source. -- Jens Axboe -- 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