linux-kernel - cache coherecy when working with cpu dcache write allocate

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: <c70ff3ad0702061031i6face64ai946d6893b960645b@mail.gmail.com>
Date:	Tue, 6 Feb 2007 20:31:58 +0200
From:	"saeed bishara" <saeed.bishara@...il.com>
To:	linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk
Subject: cache coherecy when working with cpu dcache write allocate

Hi,
    I came across data corruption problem when using xfs, my system is
arm 926, the data cache is virtually tagged and virtually indexed and
with no hw cache coherency. my CPU features the data cache write
allocate-> when doing store, the cache line of the destination address
is loaded to data cache.
  when enabling the write allocate, I got data corruption with the
xfs. the scenario is that the xfs allocates large buffer (for reading
the log records) using vmalloc, and the low level driver (raid) copies
the data to the bio vectors using the linear address, since the write
allocate is enabled,  the correct data remains on the data cache with
the linear address tag, when the IO completes, the xfs access the data
with using the vmalloc virtual address, which is different than the
kernel linear address, thus it will get a stale data!.

how should I fix this problem? I thought that only the
copy/clean_user_pages() functions should be aware to the write
allocate.

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