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:   Tue, 6 Sep 2016 11:13:56 +0200
From:   Joerg Roedel <joro@...tes.org>
To:     Baoquan He <bhe@...hat.com>
Cc:     iommu@...ts.linux-founda, linux-kernel@...r.kernel.org,
        dyoung@...hat.com
Subject: Re: io_page_fault seen in normal kernel boot log

On Mon, Sep 05, 2016 at 06:11:58PM +0800, Baoquan He wrote:
> On 09/05/16 at 11:59am, Joerg Roedel wrote:
> > > This happened on 4.8.0-rc5
> > > 
> > > [  +0.006771] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:14.4 domain=0x0009 address=0x0000000000001000 flags=0x0000]
> > > [  +0.010593] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:14.4 domain=0x0009 address=0x0000000000001040 flags=0x0000]
> > > [  +0.010596] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:14.4 domain=0x0009 address=0x0000000000001080 flags=0x0000]
> > > [  +0.010597] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:14.4 domain=0x0009 address=0x00000000000010c0 flags=0x0000]
> > > [  +0.010592] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:14.4 domain=0x0009 address=0x0000000000001100 flags=0x0000]
> > > [  +0.010592] AMD-Vi: Event logged [IO_PAGE_FAULT device=00:14.4 domain=0x0009 address=0x0000000000001140 flags=0x0000]
> > 
> > This is probably a radeon driver issue, the address looks like its
> > handed out by the IOMMU driver, so probably a use-after-free bug. I also
> > see those GPU related faults from time to time. The system usually boots
> > fine anyway. Does boot complete on that system?
> 
> Yes, except for this message, system is not impacted.

Hmm, on the other hand, the AMD-Vi driver in 4.8 uses the generic IOVA
allocator, so the addresses it hands out should be closer to 4GB.
Anyway, this is probably a bug/problem in the GPU driver.



	Joerg

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ