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  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:   Wed, 8 Aug 2018 13:02:54 +0000
From:   David Laight <David.Laight@...LAB.COM>
To:     'Catalin Marinas' <>,
        Matt Sealey <>
CC:     Mikulas Patocka <>,
        Thomas Petazzoni <>,
        Joao Pinto <>,
        Ard Biesheuvel <>,
        linux-pci <>,
        Jingoo Han <>,
        Will Deacon <>,
        Russell King <>,
        "Linux Kernel Mailing List" <>,
        linux-arm-kernel <>
Subject: RE: framebuffer corruption due to overlapping stp instructions on

From: Catalin Marinas
> Sent: 08 August 2018 13:17
> I think hazarding is what goes wrong here, especially since with
> overlapping unaligned addresses. However, I disagree that it is
> impossible to implement this properly on a platform with PCIe so that
> Normal NC mappings can be used.

I've been trying to follow this discussion...

Is the problem just that reads don't snoop/flush the write-combining buffer?
Aligned writes that end on an appropriate boundary will leave the write
combining buffer empty.
But if the buffer isn't emptied the PCIe read gets ahead of the PCIe write.

ISTR even x86 requires a fence instruction in some sequence associated
with write-combining writes.


Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

Powered by blists - more mailing lists