[pull-request] NFC updates for next-next 2026-08-17

[pull-request] NFC updates for next-next 2026-08-17

[David Heidelberg]

The following changes since commit 8d3ae59288f1e7d58d76558a6ee96d533bc5019f:

   Linux 7.2 (2026-08-16 14:32:26 -0700)

are available in the Git repository at:

   https://codeberg.org/linux-nfc/linux.git tags/nfc-net-next-20260817

for you to fetch changes up to be47ff78de05e931ede1d0a407f8ef6f063054d3:

   selftests: nci: Correct pthread_create return value check (2026-08-17 19:27:51
+0200)

----------------------------------------------------------------
NFC updates for net-next 2026-08-17

Improvements:
   nxp-nci: Add remove on IRQ error
   mrvl: spi: Unregister dev on allocation fail

Cleanups:
   Drop __maybe_unused from acpi_device_id tables
   Drop unused assignment of acpi_device_id driver data
   Initialize acpi_device_id arrays using member names
   Unify style of acpi_device_id arrays
   Initialize mei_cl_device_idarrays using member names
   Drop __maybe_unused from of_device_id tables
   Unify style of of_device_id arrays
   Drop unused assignment of spi_device_id driver data
   Initialize spi_device_idarrays using member names
   Unify style of spi_device_id arrays
   Unify style of usb_device_id arrays
   pn544: Drop empty line between i2c_device_id array and MODULE_DEVICE_TABLE()
   trf7970a: Use NULL when no response is expected

Modernization:
   st95hf: switch to using sleeping variants of gpiod API

Others:
   MAINTAINERS: Add Matrix channel to the NFC subsystem
   pn533: fix memcpy overflow warning

Signed-off-by: David Heidelberg <david@ixit.cz>

----------------------------------------------------------------
Aldo Ariel Panzardo (1):
       nfc: llcp: Fix list corruption / refcount desync in nfc_llcp_recv_dm()

Breno Leitao (2):
       nfc: llcp: avoid userspace overflow on invalid optlen
       nfc: llcp: read llcp_sock->local under the socket lock in getsockopt

Bryam Vargas (2):
       nfc: nci: add data_len bound checks to activation parameter extractors
       nfc: fdp: bound the device-reported read length and fix an skb leak

Doruk Tan Ozturk (6):
       nfc: digital: clamp SENSF_RES length to the destination buffer
       nfc: llcp: bound SNL TLV parsing to the skb and add length checks
       nfc: llcp: reject PDUs shorter than the LLCP header
       nfc: llcp: bound the connect_sn TLV walk to the skb
       nfc: st21nfca: validate ATR_REQ length against the received frame
       nfc: port100: reject frames whose declared length exceeds the received data

Lei Zhu (1):
       selftests: nci: Correct pthread_create return value check

Linmao Li (2):
       nfc: digital: Do not dump a NULL response in command completion
       nfc: nci: free destination parameters when closing a connection

Muhammad Bilal (1):
       nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers

Pengpeng Hou (3):
       nfc: microread: validate target discovery payload lengths
       nfc: nfcmrvl: validate helper command length before pull
       nfc: st21nfca: validate received frame size

Samuel Page (2):
       nfc: nci: fix out-of-bounds write in nci_target_auto_activated()
       nfc: nci: fix uninit-value in the RF discover/activated NTF handlers

Xu Rao (1):
       nfc: pn533: purge fragmented skbs during cleanup

Yinhao Hu (1):
       nfc: pn533: hold a reference to the request skb during send_frame

Yun Zhou (1):
       nfc: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing

Zhenghang Xiao (1):
       nfc: nci: fix double completion race in nci_data_exchange_complete

  drivers/nfc/fdp/i2c.c                 | 27 +++++++++++++++++++++++++++
  drivers/nfc/microread/microread.c     | 31 +++++++++++++++++++++++++++++--
  drivers/nfc/nfcmrvl/fw_dnld.c         | 11 ++++++++---
  drivers/nfc/pn533/pn533.c             | 22 ++++++++++++++++------
  drivers/nfc/port100.c                 |  7 +++++++
  drivers/nfc/st21nfca/dep.c            |  3 +++
  drivers/nfc/st21nfca/i2c.c            | 29 +++++++++++++++++++----------
  net/nfc/digital_core.c                |  2 +-
  net/nfc/digital_technology.c          |  2 ++
  net/nfc/llcp_commands.c               | 18 ++++++++++++++++--
  net/nfc/llcp_core.c                   | 69 ++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++------------
  net/nfc/llcp_sock.c                   | 14 +++++++++++---
  net/nfc/nci/data.c                    | 10 +++++-----
  net/nfc/nci/ntf.c                     | 36 ++++++++++++++++++++++++++++++------
  net/nfc/nci/rsp.c                     | 42 ++++++++++++++++++++++++++++++++++++
+++---
  tools/testing/selftests/nci/nci_dev.c | 12 +++++++-----
  16 files changed, 277 insertions(+), 58 deletions(-)

Re: [pull-request] NFC updates for next-next 2026-08-17

[Jakub Kicinski]

On Mon, 17 Aug 2026 19:45:45 +0200 David Heidelberg wrote:
> The following changes since commit 8d3ae59288f1e7d58d76558a6ee96d533bc5019f:
> 
>    Linux 7.2 (2026-08-16 14:32:26 -0700)
> 
> are available in the Git repository at:
> 
>    https://codeberg.org/linux-nfc/linux.git tags/nfc-net-next-20260817

Please don't rebase your trees. The base of your tree should be at
whatever point net-next was after the previous PR to net-next.
Because:
 - we don't have the 7.2 tag in our trees yet, if I merge this it will
   look like I pulled a week worth of Linus's tree, not a small PR from
   you
 - the commit hashes in linux-next do not match what you have in this PR

Did you rebase this tree recently? Perhaps you still have the previous
version in git reflog that we could pull instead? Exceptionally, this
time you may need to rebase to go back to an older base..

BTW normally to get your own fixes into your own -next tree you should
stagger the PRs - first send the fixes, after net -> net-next merge on
Thu afternoon - send the -next PR.

Re: [pull-request] NFC updates for next-next 2026-08-17

[David Heidelberg]

On 17/08/2026 20:53, Jakub Kicinski wrote:
> On Mon, 17 Aug 2026 19:45:45 +0200 David Heidelberg wrote:
>> The following changes since commit 8d3ae59288f1e7d58d76558a6ee96d533bc5019f:
>>
>>     Linux 7.2 (2026-08-16 14:32:26 -0700)
>>
>> are available in the Git repository at:
>>
>>     https://codeberg.org/linux-nfc/linux.git tags/nfc-net-next-20260817
> 
> Please don't rebase your trees. The base of your tree should be at
> whatever point net-next was after the previous PR to net-next.
> Because:
>   - we don't have the 7.2 tag in our trees yet, if I merge this it will
>     look like I pulled a week worth of Linus's tree, not a small PR from
>     you
>   - the commit hashes in linux-next do not match what you have in this PR
> 
> Did you rebase this tree recently? Perhaps you still have the previous
> version in git reflog that we could pull instead? Exceptionally, this
> time you may need to rebase to go back to an older base..

Yes I have, let me tag the rc8 instead.

David>
> BTW normally to get your own fixes into your own -next tree you should
> stagger the PRs - first send the fixes, after net -> net-next merge on
> Thu afternoon - send the -next PR.
>