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: dmaengine: avoid map_cnt overflow with CONFIG_DMA_ENGINE_RAID
Date: Mon, 5 Feb 2018 11:09:25 +0530 [thread overview]
Message-ID: <20180205053925.GQ18649@localhost> (raw)
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
WARNING: multiple messages have this Message-ID (diff)
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
Date: Mon, 5 Feb 2018 11:09:25 +0530 [thread overview]
Message-ID: <20180205053925.GQ18649@localhost> (raw)
In-Reply-To: <20180108155050.7387-1-zi.yan@sent.com>
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
next reply other threads:[~2018-02-05 5:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-05 5:39 Vinod Koul [this message]
2018-02-05 5:39 ` [PATCH] dmaengine: avoid map_cnt overflow with CONFIG_DMA_ENGINE_RAID Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2018-01-16 20:00 Zi Yan
2018-01-16 20:00 ` [PATCH] " Zi Yan
2018-01-12 16:56 Vinod Koul
2018-01-12 16:56 ` [PATCH] " Vinod Koul
2018-01-08 15:50 Zi Yan
2018-01-08 15:50 ` [PATCH] " Zi Yan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180205053925.GQ18649@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zi.yan@cs.rutgers.edu \
--cc=zi.yan@sent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.