Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 5 Feb 2018 11:09:25 +0530
From:   Vinod Koul <vinod.koul@intel.com>
To:     Zi Yan <zi.yan@sent.com>
Cc:     dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
        Zi Yan <zi.yan@cs.rutgers.edu>,
        Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] dmaengine: avoid map_cnt overflow with
 CONFIG_DMA_ENGINE_RAID
Message-ID: <20180205053925.GQ18649@localhost>
References: <20180108155050.7387-1-zi.yan@sent.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180108155050.7387-1-zi.yan@sent.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, Jan 08, 2018 at 10:50:50AM -0500, Zi Yan wrote:
> From: Zi Yan <zi.yan@cs.rutgers.edu>
> 
> When CONFIG_DMA_ENGINE_RAID is enabled, unmap pool size can reach to
> 256. But in struct dmaengine_unmap_data, map_cnt is only u8, wrapping
> to 0, if the unmap pool is maximally used. This triggers BUG() when
> struct dmaengine_unmap_data is freed. Use u16 to fix the problem.

Applied, thanks

-- 
~Vinod