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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161206045954.GO6408@localhost>
Date:   Tue, 6 Dec 2016 10:29:54 +0530
From:   Vinod Koul <vinod.koul@...el.com>
To:     Pan Bian <bianpan2016@....com>
Cc:     Dan Williams <dan.j.williams@...el.com>,
        Dave Jiang <dave.jiang@...el.com>,
        Julia Lawall <Julia.Lawall@...6.fr>, dmaengine@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] dmaengine: ioat: set error code on failures

On Fri, Dec 02, 2016 at 10:49:01PM +0800, Pan Bian wrote:
> In function ioat_dma_self_test(), when the calls to dma_mapping_error() 
> fails, the value of return variable err is 0 (indicates no error). As a 
> result, the return value may be inconsistent with the execution status. 
> This patch fixes the bug by assigning -ENOMEM to err on the error path.

This was v2 of the series so you should tag it as PATCH v2. You can do so
with --subject-prefix in git format-patch command.

Applied both now with Dave's Acks

-- 
~Vinod

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ