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] [day] [month] [year] [list]
Message-Id: 
 <171741963022.17349.8989919081821118644.git-patchwork-notify@kernel.org>
Date: Mon, 03 Jun 2024 13:00:30 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Thorsten Blum <thorsten.blum@...lux.com>
Cc: marcel@...tmann.org, luiz.dentz@...il.com,
 linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Bluetooth: btintel_pcie: Remove unnecessary memset(0) calls

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@...el.com>:

On Sat,  1 Jun 2024 01:51:33 +0200 you wrote:
> Remove memset(0) after dma_alloc_coherent(), which already zeroes out
> the memory, and fix the following two Coccinelle/coccicheck warnings
> reported by zalloc-simple.cocci:
> 
> btintel_pcie.c:837:19-37: WARNING: dma_alloc_coherent used in
> 
> 	/* Allocate full chunk of data buffer for DMA first and do indexing and
> 	 * initialization next, so it can be freed easily
> 	 */
> 	rxq->buf_v_addr   already zeroes out memory, so memset is not needed
> 
> [...]

Here is the summary with links:
  - Bluetooth: btintel_pcie: Remove unnecessary memset(0) calls
    https://git.kernel.org/bluetooth/bluetooth-next/c/c137bc53035c

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ