linux-kernel - Re: [PATCH 1/3] Fix COW D-cache aliasing on fork

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 20 Oct 2006 09:36:57 -0700 (PDT)
From:	Linus Torvalds <torvalds@...l.org>
To:	Nick Piggin <nickpiggin@...oo.com.au>
cc:	David Miller <davem@...emloft.net>, ralf@...ux-mips.org,
	akpm@...l.org, linux-kernel@...r.kernel.org, anemo@....ocn.ne.jp
Subject: Re: [PATCH 1/3] Fix COW D-cache aliasing on fork

On Sat, 21 Oct 2006, Nick Piggin wrote:
> 
> I didn't think that would work if there is no TLB. But if the writeback
> can cause a TLB reload, and then bypass the readonly protection, then
> yes would close all races.

On the other hand, doing the cache flush at COW time is "kind of 
equivalent" to just doing it after the TLB flush. It's now just _much_ 
after the flush ;)

So maybe the COW D$ aliasing patch-series is just the right thing to do. 
Not worry about D$ at _all_ when doing the actual fork, and only worry 
about it on an actual COW event. Hmm?

		Linus
-
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/