linux-kernel - Re: [PATCH v3] nfc: hci: pass callback data param as pointer in nci

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: <162791400750.18419.3531561992313522609.git-patchwork-notify@kernel.org>
Date:   Mon, 02 Aug 2021 14:20:07 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
Cc:     davem@...emloft.net, kuba@...nel.org, bongsu.jeon@...sung.com,
        linux-nfc@...ts.01.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] nfc: hci: pass callback data param as pointer in
 nci_request()

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Sat, 31 Jul 2021 12:21:44 +0200 you wrote:
> The nci_request() receives a callback function and unsigned long data
> argument "opt" which is passed to the callback.  Almost all of the
> nci_request() callers pass pointer to a stack variable as data argument.
> Only few pass scalar value (e.g. u8).
> 
> All such callbacks do not modify passed data argument and in previous
> commit they were made as const.  However passing pointers via unsigned
> long removes the const annotation.  The callback could simply cast
> unsigned long to a pointer to writeable memory.
> 
> [...]

Here is the summary with links:
  - [v3] nfc: hci: pass callback data param as pointer in nci_request()
    https://git.kernel.org/netdev/net-next/c/35d7a6f1fb53

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html