All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Michael Thalmeier <michael.thalmeier@hale.at>
Cc: deepak.sharma.472935@gmail.com, krzk@kernel.org,
	vadim.fedorenko@linux.dev, horms@kernel.org, pabeni@redhat.com,
	kuba@kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, kernel@0x83.eu, michael@thalmeier.at,
	stable@vger.kernel.org
Subject: Re: [PATCH net v6] net: nfc: nci: Fix parameter validation for packet data
Date: Thu, 19 Feb 2026 17:40:16 +0000	[thread overview]
Message-ID: <177152281658.2317554.15811337395929240239.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260218083000.301354-1-michael.thalmeier@hale.at>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 18 Feb 2026 09:30:00 +0100 you wrote:
> Since commit 9c328f54741b ("net: nfc: nci: Add parameter validation for
> packet data") communication with nci nfc chips is not working any more.
> 
> The mentioned commit tries to fix access of uninitialized data, but
> failed to understand that in some cases the data packet is of variable
> length and can therefore not be compared to the maximum packet length
> given by the sizeof(struct).
> 
> [...]

Here is the summary with links:
  - [net,v6] net: nfc: nci: Fix parameter validation for packet data
    https://git.kernel.org/netdev/net/c/571dcbeb8e63

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



      parent reply	other threads:[~2026-02-19 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-18  8:30 [PATCH net v6] net: nfc: nci: Fix parameter validation for packet data Michael Thalmeier
2026-02-18  8:50 ` Krzysztof Kozlowski
2026-02-19 17:40 ` patchwork-bot+netdevbpf [this message]

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=177152281658.2317554.15811337395929240239.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=deepak.sharma.472935@gmail.com \
    --cc=horms@kernel.org \
    --cc=kernel@0x83.eu \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.thalmeier@hale.at \
    --cc=michael@thalmeier.at \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=vadim.fedorenko@linux.dev \
    /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.