All of lore.kernel.org
 help / color / mirror / Atom feed
* kasan warning related to hwmon/acpi, 5.13.5+
@ 2021-07-28 19:29 Ben Greear
  2021-07-30 22:23 ` Ben Greear
  0 siblings, 1 reply; 2+ messages in thread
From: Ben Greear @ 2021-07-28 19:29 UTC (permalink / raw)
  To: Linux Kernel Mailing List

Hello,

I'm seeing this warning often right after/during boot, but not always.
I am pretty sure this is not some regression I've added to my tree, but
of course that is possible.

If someone has already got a fix for this or debugged it, please let me know.

Jul 28 12:23:08 ct523c-0b29 kernel: ==================================================================
Jul 28 12:23:08 ct523c-0b29 kernel: BUG: KASAN: use-after-free in string_nocheck+0x9d/0x160
Jul 28 12:23:08 ct523c-0b29 kernel: Read of size 1 at addr ffff88810ac29820 by task sadc/1243
Jul 28 12:23:08 ct523c-0b29 kernel:
Jul 28 12:23:08 ct523c-0b29 kernel: CPU: 4 PID: 1243 Comm: sadc Not tainted 5.13.5+ #37
Jul 28 12:23:08 ct523c-0b29 kernel: Hardware name: Default string Default string/SKYBAY, BIOS 5.12 02/19/2019
Jul 28 12:23:08 ct523c-0b29 kernel: Call Trace:
Jul 28 12:23:08 ct523c-0b29 kernel:  dump_stack+0x9b/0xce
Jul 28 12:23:08 ct523c-0b29 kernel:  ? string_nocheck+0x9d/0x160
Jul 28 12:23:08 ct523c-0b29 kernel:  print_address_description.constprop.9+0x3a/0x60
Jul 28 12:23:08 ct523c-0b29 kernel:  ? string_nocheck+0x9d/0x160
Jul 28 12:23:08 ct523c-0b29 kernel:  ? string_nocheck+0x9d/0x160
Jul 28 12:23:08 ct523c-0b29 kernel:  kasan_report.cold.14+0x7c/0xd8
Jul 28 12:23:08 ct523c-0b29 kernel:  ? string_nocheck+0x9d/0x160
Jul 28 12:23:08 ct523c-0b29 kernel:  string_nocheck+0x9d/0x160
Jul 28 12:23:08 ct523c-0b29 kernel:  ? widen_string+0x160/0x160
Jul 28 12:23:08 ct523c-0b29 kernel:  ? string_nocheck+0x160/0x160
Jul 28 12:23:08 ct523c-0b29 kernel:  string+0xb6/0xc0
Jul 28 12:23:08 ct523c-0b29 kernel:  ? netdev_bits+0x170/0x170
Jul 28 12:23:08 ct523c-0b29 kernel:  vsnprintf+0x20c/0x780
Jul 28 12:23:08 ct523c-0b29 kernel:  ? unwind_get_return_address+0x2a/0x40
Jul 28 12:23:08 ct523c-0b29 kernel:  ? pointer+0x540/0x540
Jul 28 12:23:08 ct523c-0b29 kernel:  sprintf+0x9e/0xd0
Jul 28 12:23:08 ct523c-0b29 kernel:  ? scnprintf+0xf0/0xf0
Jul 28 12:23:08 ct523c-0b29 kernel:  ? name_show+0x11/0x30 [hwmon]
Jul 28 12:23:08 ct523c-0b29 kernel:  name_show+0x24/0x30 [hwmon]
Jul 28 12:23:08 ct523c-0b29 kernel:  dev_attr_show+0x2f/0x60
Jul 28 12:23:08 ct523c-0b29 kernel:  sysfs_kf_seq_show+0x114/0x1f0
Jul 28 12:23:08 ct523c-0b29 kernel:  ? device_remove_bin_file+0x10/0x10
Jul 28 12:23:08 ct523c-0b29 kernel:  seq_read_iter+0x25c/0x6d0
Jul 28 12:23:08 ct523c-0b29 kernel:  new_sync_read+0x248/0x360
Jul 28 12:23:08 ct523c-0b29 kernel:  ? __x64_sys_llseek+0x1d0/0x1d0
Jul 28 12:23:08 ct523c-0b29 kernel:  ? __ia32_sys_lstat+0x30/0x30
Jul 28 12:23:08 ct523c-0b29 kernel:  ? __fsnotify_parent+0x3a8/0x540
Jul 28 12:23:08 ct523c-0b29 kernel:  ? fsnotify+0x7d0/0x7d0
Jul 28 12:23:08 ct523c-0b29 kernel:  ? kernfs_iop_getattr+0x6c/0x80
Jul 28 12:23:08 ct523c-0b29 kernel:  vfs_read+0x14f/0x220
Jul 28 12:23:08 ct523c-0b29 kernel:  ksys_read+0xaf/0x140
Jul 28 12:23:08 ct523c-0b29 kernel:  ? vfs_write+0x360/0x360
Jul 28 12:23:08 ct523c-0b29 kernel:  ? __audit_syscall_entry+0x19b/0x200
Jul 28 12:23:08 ct523c-0b29 kernel:  ? ktime_get_coarse_real_ts64+0x4c/0x70
Jul 28 12:23:08 ct523c-0b29 kernel:  do_syscall_64+0x36/0xa0
Jul 28 12:23:08 ct523c-0b29 kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
Jul 28 12:23:08 ct523c-0b29 kernel: RIP: 0033:0x7fe9fe559145
Jul 28 12:23:08 ct523c-0b29 kernel: Code: fe ff ff 50 48 8d 3d ca fb 09 00 e8 a5 eb 01 00 0f 1f 44 00 00 f3 0f 1e fa 48 8d 05 15 84 0d 00 8b 00 85 c0 75 0f 31 
c0 0f 05 <48> 3d 00 f0 ff ff 77 53 c3 66 90 48 83 ec 28 48 89 54 24 18 48 89
Jul 28 12:23:08 ct523c-0b29 kernel: RSP: 002b:00007ffcfa5f0d28 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
Jul 28 12:23:08 ct523c-0b29 kernel: RAX: ffffffffffffffda RBX: 00000000021712e0 RCX: 00007fe9fe559145
Jul 28 12:23:08 ct523c-0b29 kernel: RDX: 0000000000001000 RSI: 000000000217bf80 RDI: 0000000000000004
Jul 28 12:23:08 ct523c-0b29 kernel: RBP: 0000000000000d68 R08: 0000000000000004 R09: 000000000000006f
Jul 28 12:23:08 ct523c-0b29 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007fe9fe628800
Jul 28 12:23:08 ct523c-0b29 kernel: R13: 00007fe9fe629400 R14: 00007ffcfa5f0e10 R15: 000000000000007f
Jul 28 12:23:08 ct523c-0b29 kernel:
Jul 28 12:23:08 ct523c-0b29 kernel: Allocated by task 1:
Jul 28 12:23:08 ct523c-0b29 kernel:  kasan_save_stack+0x19/0x40
Jul 28 12:23:08 ct523c-0b29 kernel:  __kasan_kmalloc+0x7f/0xa0
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_ns_internalize_name+0xb2/0x120
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_ns_get_node_unlocked+0xfd/0x18c
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_ns_get_node+0x3b/0x50
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_get_handle+0xeb/0x13a
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_has_method+0x5a/0x90
Jul 28 12:23:08 ct523c-0b29 kernel:  acpiphp_add_context+0x498/0x650
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_ns_walk_namespace+0xfa/0x1f3
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_walk_namespace+0x95/0xbd
Jul 28 12:23:08 ct523c-0b29 kernel:  acpiphp_enumerate_slots+0x269/0x3b0
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_pci_add_bus+0x94/0x170
Jul 28 12:23:08 ct523c-0b29 kernel:  pci_register_host_bridge+0x485/0x540
Jul 28 12:23:08 ct523c-0b29 kernel:  pci_create_root_bus+0x121/0x160
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_pci_root_create+0x1c3/0x390
Jul 28 12:23:08 ct523c-0b29 kernel:  pci_acpi_scan_root+0x2b8/0x2d0
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_pci_root_add.cold.12+0xb0/0x752
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_bus_attach+0x26a/0x4b0
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_bus_attach+0x122/0x4b0
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_bus_attach+0x122/0x4b0
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_bus_scan+0x8f/0x150
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_scan_init+0x1a6/0x3ca
Jul 28 12:23:08 ct523c-0b29 kernel:  acpi_init+0x581/0x60e
Jul 28 12:23:08 ct523c-0b29 kernel:  do_one_initcall+0x82/0x290
Jul 28 12:23:08 ct523c-0b29 kernel:  kernel_init_freeable+0x347/0x3d8
Jul 28 12:23:08 ct523c-0b29 kernel:  kernel_init+0x7/0x10d
Jul 28 12:23:08 ct523c-0b29 kernel:  ret_from_fork+0x1f/0x30
Jul 28 12:23:08 ct523c-0b29 kernel:
Jul 28 12:23:08 ct523c-0b29 kernel: The buggy address belongs to the object at ffff88810ac29820
                                      which belongs to the cache kmalloc-8 of size 8
Jul 28 12:23:08 ct523c-0b29 kernel: The buggy address is located 0 bytes inside of
                                      8-byte region [ffff88810ac29820, ffff88810ac29828)
Jul 28 12:23:08 ct523c-0b29 kernel: The buggy address belongs to the page:
Jul 28 12:23:08 ct523c-0b29 kernel: page:00000000347308e1 refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff88810ac29820 pfn:0x10ac29
Jul 28 12:23:08 ct523c-0b29 kernel: flags: 0x5fff8000000200(slab|node=0|zone=2|lastcpupid=0x3fff)
Jul 28 12:23:08 ct523c-0b29 kernel: raw: 005fff8000000200 ffffea000428ab00 0000000a0000000a ffff888108042280
Jul 28 12:23:08 ct523c-0b29 kernel: raw: ffff88810ac29820 0000000080660051 00000001ffffffff 0000000000000000
Jul 28 12:23:08 ct523c-0b29 kernel: page dumped because: kasan: bad access detected
Jul 28 12:23:08 ct523c-0b29 kernel:
Jul 28 12:23:08 ct523c-0b29 kernel: Memory state around the buggy address:
Jul 28 12:23:08 ct523c-0b29 kernel:  ffff88810ac29700: fc 00 fc fc fc fc 00 fc fc fc fc 00 fc fc fc fc
Jul 28 12:23:08 ct523c-0b29 kernel:  ffff88810ac29780: 00 fc fc fc fc 00 fc fc fc fc 00 fc fc fc fc 00
Jul 28 12:23:08 ct523c-0b29 kernel: >ffff88810ac29800: fc fc fc fc fb fc fc fc fc 00 fc fc fc fc fb fc
Jul 28 12:23:08 ct523c-0b29 kernel:                                ^
Jul 28 12:23:08 ct523c-0b29 kernel:  ffff88810ac29880: fc fc fc fb fc fc fc fc fb fc fc fc fc fb fc fc
Jul 28 12:23:08 ct523c-0b29 kernel:  ffff88810ac29900: fc fc 00 fc fc fc fc 00 fc fc fc fc 00 fc fc fc
Jul 28 12:23:08 ct523c-0b29 kernel: ==================================================================
Jul 28 12:23:08 ct523c-0b29 kernel: Disabling lock debugging due to kernel taint


Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: kasan warning related to hwmon/acpi, 5.13.5+
  2021-07-28 19:29 kasan warning related to hwmon/acpi, 5.13.5+ Ben Greear
@ 2021-07-30 22:23 ` Ben Greear
  0 siblings, 0 replies; 2+ messages in thread
From: Ben Greear @ 2021-07-30 22:23 UTC (permalink / raw)
  To: Linux Kernel Mailing List

On 7/28/21 12:29 PM, Ben Greear wrote:
> Hello,
> 
> I'm seeing this warning often right after/during boot, but not always.
> I am pretty sure this is not some regression I've added to my tree, but
> of course that is possible.
> 
> If someone has already got a fix for this or debugged it, please let me know.

Root cause of this was mt7915 driver, a fix has been posted...

Thanks,
Ben


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-07-30 22:30 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-28 19:29 kasan warning related to hwmon/acpi, 5.13.5+ Ben Greear
2021-07-30 22:23 ` Ben Greear

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.