From: patchwork-bot+netdevbpf@kernel.org
To: Thadeu Lima de Souza Cascardo <cascardo@igalia.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
eadavis@qq.com, davem@davemloft.net, krzk@kernel.org,
bongsu.jeon@samsung.com, kernel-dev@igalia.com
Subject: Re: [PATCH net] Revert "nfc/nci: Add the inconsistency check between the input data length and count"
Date: Mon, 19 Jan 2026 14:18:28 +0000 [thread overview]
Message-ID: <176883230827.1426077.9411051878811984292.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260113202458.449455-1-cascardo@igalia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 13 Jan 2026 17:24:58 -0300 you wrote:
> This reverts commit 068648aab72c9ba7b0597354ef4d81ffaac7b979.
>
> NFC packets may have NUL-bytes. Checking for string length is not a correct
> assumption here. As long as there is a check for the length copied from
> copy_from_user, all should be fine.
>
> The fix only prevented the syzbot reproducer from triggering the bug
> because the packet is not enqueued anymore and the code that triggers the
> bug is not exercised.
>
> [...]
Here is the summary with links:
- [net] Revert "nfc/nci: Add the inconsistency check between the input data length and count"
https://git.kernel.org/netdev/net/c/f40ddcc0c0ca
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-19 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 20:24 [PATCH net] Revert "nfc/nci: Add the inconsistency check between the input data length and count" Thadeu Lima de Souza Cascardo
2026-01-19 14:18 ` 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=176883230827.1426077.9411051878811984292.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bongsu.jeon@samsung.com \
--cc=cascardo@igalia.com \
--cc=davem@davemloft.net \
--cc=eadavis@qq.com \
--cc=kernel-dev@igalia.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox