linux-kernel - Help with implementing some form of barriers in 3.0 kernels.

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-next>] [day] [month] [year] [list]

Message-ID: <20110907174832.GN32190@dumpdata.com>
Date:	Wed, 7 Sep 2011 13:48:32 -0400
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	hch@...radead.org
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>, jbeulich@...ell.com,
	linux-kernel@...r.kernel.org, JBeulich@...e.com
Subject: Help with implementing some form of barriers in 3.0 kernels.

Hey Christoph,

I was wondering what you think is the proper way of implementing a
backend to support the 'barrier' type requests? We have this issue were
there are 2.6.36 type guests that still use barriers and we would like
to support them properly. But in 3.0 there are no barriers - hence
the question whether WRITE_fLUSH_FUA would be equal to WRITE_BARRIER?

Or is there some other things that we should take in consideration?

Thanks!
--
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/