From: patchwork-bot+netdevbpf@kernel.org
To: Ziyang Xuan (William) <william.xuanziyang@huawei.com>
Cc: mani@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net v2] net: qrtr: Fix an uninit variable access bug in qrtr_tx_resume()
Date: Thu, 13 Apr 2023 07:50:17 +0000 [thread overview]
Message-ID: <168137221767.12270.4741360777654214045.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230410012352.3997823-1-william.xuanziyang@huawei.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 10 Apr 2023 09:23:52 +0800 you wrote:
> Syzbot reported a bug as following:
>
> =====================================================
> BUG: KMSAN: uninit-value in qrtr_tx_resume+0x185/0x1f0 net/qrtr/af_qrtr.c:230
> qrtr_tx_resume+0x185/0x1f0 net/qrtr/af_qrtr.c:230
> qrtr_endpoint_post+0xf85/0x11b0 net/qrtr/af_qrtr.c:519
> qrtr_tun_write_iter+0x270/0x400 net/qrtr/tun.c:108
> call_write_iter include/linux/fs.h:2189 [inline]
> aio_write+0x63a/0x950 fs/aio.c:1600
> io_submit_one+0x1d1c/0x3bf0 fs/aio.c:2019
> __do_sys_io_submit fs/aio.c:2078 [inline]
> __se_sys_io_submit+0x293/0x770 fs/aio.c:2048
> __x64_sys_io_submit+0x92/0xd0 fs/aio.c:2048
> do_syscall_x64 arch/x86/entry/common.c:50 [inline]
> do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
> entry_SYSCALL_64_after_hwframe+0x63/0xcd
>
> [...]
Here is the summary with links:
- [net,v2] net: qrtr: Fix an uninit variable access bug in qrtr_tx_resume()
https://git.kernel.org/netdev/net/c/6417070918de
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:[~2023-04-13 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 1:23 [PATCH net v2] net: qrtr: Fix an uninit variable access bug in qrtr_tx_resume() Ziyang Xuan
2023-04-10 8:20 ` Simon Horman
2023-04-13 7:50 ` 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=168137221767.12270.4741360777654214045.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mani@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=william.xuanziyang@huawei.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 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.