[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<170525102408.11320.1615500877884972571.git-patchwork-notify@kernel.org>
Date: Sun, 14 Jan 2024 16:50:24 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Nikita Yushchenko <nikita.yoush@...entembedded.com>
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
s.shtylyov@....ru, claudiu.beznea.uj@...renesas.com,
yoshihiro.shimoda.uh@...esas.com, wsa+renesas@...g-engineering.com,
u.kleine-koenig@...gutronix.de, netdev@...r.kernel.org,
linux-renesas-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: ravb: Fix dma_addr_t truncation in error case
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@...emloft.net>:
On Sat, 13 Jan 2024 10:22:21 +0600 you wrote:
> In ravb_start_xmit(), ravb driver uses u32 variable to store result of
> dma_map_single() call. Since ravb hardware has 32-bit address fields in
> descriptors, this works properly when mapping is successful - it is
> platform's job to provide mapping addresses that fit into hardware
> limitations.
>
> However, in failure case dma_map_single() returns DMA_MAPPING_ERROR
> constant that is 64-bit when dma_addr_t is 64-bit. Storing this constant
> in u32 leads to truncation, and further call to dma_mapping_error()
> fails to notice the error.
>
> [...]
Here is the summary with links:
- net: ravb: Fix dma_addr_t truncation in error case
https://git.kernel.org/netdev/net/c/e327b2372bc0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists