public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Ye Bin <yebin@huaweicloud.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
	luiz.dentz@gmail.com, ricardo@marliere.net,
	linux-bluetooth@vger.kernel.org, viro@zeniv.linux.org.uk,
	yebin10@huawei.com, zhangxiaoxu5@huawei.com
Subject: Re: [PATCH] Bluetooth: bnep: fix wild-memory-access in proto_unregister
Date: Wed, 16 Oct 2024 16:00:31 +0000	[thread overview]
Message-ID: <172909443152.1863747.16466588010493150746.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241014090708.3818916-1-yebin@huaweicloud.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Mon, 14 Oct 2024 17:07:08 +0800 you wrote:
> From: Ye Bin <yebin10@huawei.com>
> 
> There's issue as follows:
>   KASAN: maybe wild-memory-access in range [0xdead...108-0xdead...10f]
>   CPU: 3 UID: 0 PID: 2805 Comm: rmmod Tainted: G        W
>   RIP: 0010:proto_unregister+0xee/0x400
>   Call Trace:
>    <TASK>
>    __do_sys_delete_module+0x318/0x580
>    do_syscall_64+0xc1/0x1d0
>    entry_SYSCALL_64_after_hwframe+0x77/0x7f
> 
> [...]

Here is the summary with links:
  - Bluetooth: bnep: fix wild-memory-access in proto_unregister
    https://git.kernel.org/bluetooth/bluetooth-next/c/7902a76b54e3

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



      reply	other threads:[~2024-10-16 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14  9:07 [PATCH] Bluetooth: bnep: fix wild-memory-access in proto_unregister Ye Bin
2024-10-16 16:00 ` patchwork-bot+bluetooth [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=172909443152.1863747.16466588010493150746.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=ricardo@marliere.net \
    --cc=viro@zeniv.linux.org.uk \
    --cc=yebin10@huawei.com \
    --cc=yebin@huaweicloud.com \
    --cc=zhangxiaoxu5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox