From: patchwork-bot+bluetooth@kernel.org
To: Kiran K <kiran.k@intel.com>
Cc: linux-bluetooth@vger.kernel.org, ravishankar.srivatsa@intel.com,
lokendra.singh@intel.com, chethan.tumkur.narayan@intel.com
Subject: Re: [PATCH v1] Bluetooth: btinel: Check ACPI handle for NULL before accessing
Date: Fri, 10 Mar 2023 00:20:17 +0000 [thread overview]
Message-ID: <167840761786.25154.15943833396609314301.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230308075837.5559-1-kiran.k@intel.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 8 Mar 2023 13:28:37 +0530 you wrote:
> Older platforms and Virtual platforms which doesn't have support for
> bluetooth device in ACPI firmware will not have valid ACPI handle. Check
> for validity of handle before accessing.
>
> dmesg log from simics environment (virtual platform):
>
> BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
> IP: acpi_ns_walk_namespace+0x5c/0x278
> PGD 0 P4D 0
> Oops: 0000 [#1] SMP PTI
> Modules linked in: bnep intel_powerclamp coretemp kvm_intel kvm irqbypass intel_cstate input_leds joydev serio_raw mac_hid btusb(OE) btintel(OE) bluetooth(OE) lpc_ich compat(OE) ecdh_generic i7core_edac i5500_temp shpchp binfmt_misc sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid e1000e psmouse ahci pata_acpi libahci ptp pps_core floppy
> CPU: 0 PID: 35 Comm: kworker/u3:0 Tainted: G OE 4.15.0-140-generic #144-Ubuntu
> Hardware name: Simics Simics, BIOS Simics 01/01/2011
> Workqueue: hci0 hci_power_on [bluetooth]
> RIP: 0010:acpi_ns_walk_namespace+0x5c/0x278
> RSP: 0000:ffffaa9c0049bba8 EFLAGS: 00010246
> RAX: 0000000000000001 RBX: 0000000000001001 RCX: 0000000000000010
> RDX: ffffffff92ea7e27 RSI: ffffffff92ea7e10 RDI: 00000000000000c8
> RBP: ffffaa9c0049bbf8 R08: 0000000000000000 R09: ffffffffc05b39d0
> R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000001
> R13: 0000000000000000 R14: ffffffffc05b39d0 R15: ffffaa9c0049bc70
> FS: 0000000000000000(0000) GS:ffff8be73fc00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000000000018 CR3: 0000000075f0e000 CR4: 00000000000006f0
>
> [...]
Here is the summary with links:
- [v1] Bluetooth: btinel: Check ACPI handle for NULL before accessing
https://git.kernel.org/bluetooth/bluetooth-next/c/44f771148fb8
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-03-10 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 7:58 [PATCH v1] Bluetooth: btinel: Check ACPI handle for NULL before accessing Kiran K
2023-03-08 8:40 ` [v1] " bluez.test.bot
2023-03-10 0:20 ` 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=167840761786.25154.15943833396609314301.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lokendra.singh@intel.com \
--cc=ravishankar.srivatsa@intel.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