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: <5638E553.6050400@codeaurora.org>
Date:	Tue, 3 Nov 2015 10:48:19 -0600
From:	Timur Tabi <timur@...eaurora.org>
To:	Vinod Koul <vinod.koul@...el.com>
Cc:	Sinan Kaya <okaya@...eaurora.org>, 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

Vinod Koul wrote:
> Failing politely would be right thing to do. If DMA starts sending data to
> anywhere in system memory due to bug or wrong addresses we can't do
> anything to prevent that

My point is that I have a hard time believing that a DMA failure would 
likely result the driver politely detecting the problem and exiting 
properly.  I just don't think it's realistic to expect that.

Now maybe it's better for a catastrophic failure to occur when the 
driver loads instead of during some critical network operation.

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