From: patchwork-bot+netdevbpf@kernel.org
To: Edward Adam Davis <eadavis@qq.com>
Cc: syzbot+71bfed2b2bcea46c98f2@syzkaller.appspotmail.com,
davem@davemloft.net, edumazet@google.com, krzk@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] nfc/nci: Add the inconsistency check between the input data length and count
Date: Wed, 29 May 2024 12:10:29 +0000 [thread overview]
Message-ID: <171698462989.27277.5441892226443327957.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_53E8065F49BD2ECD2EC28C9AE7EC86EC5206@qq.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 28 May 2024 11:12:31 +0800 you wrote:
> write$nci(r0, &(0x7f0000000740)=ANY=[@ANYBLOB="610501"], 0xf)
>
> Syzbot constructed a write() call with a data length of 3 bytes but a count value
> of 15, which passed too little data to meet the basic requirements of the function
> nci_rf_intf_activated_ntf_packet().
>
> Therefore, increasing the comparison between data length and count value to avoid
> problems caused by inconsistent data length and count.
>
> [...]
Here is the summary with links:
- nfc/nci: Add the inconsistency check between the input data length and count
https://git.kernel.org/netdev/net/c/068648aab72c
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:[~2024-05-29 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 0:33 [syzbot] [nfc?] [net?] KMSAN: uninit-value in nci_ntf_packet (2) syzbot
2024-05-28 2:14 ` Edward Adam Davis
2024-05-28 2:50 ` syzbot
2024-05-28 3:12 ` [PATCH] nfc/nci: Add the inconsistency check between the input data length and count Edward Adam Davis
2024-05-29 12:10 ` 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=171698462989.27277.5441892226443327957.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=eadavis@qq.com \
--cc=edumazet@google.com \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+71bfed2b2bcea46c98f2@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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