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]
Message-ID: <5638E4EA.1040905@codeaurora.org>
Date:	Tue, 3 Nov 2015 10:46:34 -0600
From:	Timur Tabi <timur@...eaurora.org>
To:	Sinan Kaya <okaya@...eaurora.org>,
	Vinod Koul <vinod.koul@...el.com>
Cc:	dmaengine@...r.kernel.org, cov@...eaurora.org, jcm@...hat.com,
	Dan Williams <dan.j.williams@...el.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 2/3] dmaselftest: add memcpy selftest support functions

Sinan Kaya wrote:
> 1. Bug in ARM64 DMA subsystem.
> 2. Bug in IOMMU driver.
> 3. Bug in another newly introduced driver. The new driver would hog the
> CPU and won't allow HIDMA interrupts to execute. Therefore, the test
> times out.

Which driver?

Wouldn't these problems already be exposed by dmatest?  I was asking 
whether it's possible that, every now and then, your DMA internal test 
could fail and then the driver would unload.  I'm not talking about hard 
bugs in other code that always causes the DMA driver test to fail.

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ