From: bugzilla-daemon@kernel.org
To: linux-iio@vger.kernel.org
Subject: [Bug 220772] NULL pointer dereference in bmc150-accel-core
Date: Sat, 15 Nov 2025 18:25:37 +0000 [thread overview]
Message-ID: <bug-220772-217253-6YvaYGoAZn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220772-217253@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220772
--- Comment #4 from Jonathan Cameron (jic23@kernel.org) ---
On Wed, 12 Nov 2025 01:46:52 +0000
bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=220772
>
> --- Comment #3 from Vitaliy Tomin (highwaystar.ru@gmail.com) ---
> (In reply to Jonathan Cameron from comment #2)
> > On Sun, 09 Nov 2025 19:59:38 +0000
> > bugzilla-daemon@kernel.org wrote:
>
> > Could you share the names of the triggers under
> > /sys/bus/iio/devices/trigger*/name
> > and
> > cat /proc/interrupts
> >
> > Maybe the tooling is using an hrtimer or sysfs trigger but the
> > driver seems to have a validate_trigger callback that should prevent that
> > so I think we need a little more information.
> >
> > Thanks
> >
> > Jonathan
>
>
> There is no such files here:
Thanks. So to hit the buffer functions is must be in fifo mode
(which runs without a trigger).
Seems the conversation around the original fix should have gone
on a bit longer as it was correct as we do want to enable buffered
support if no interrupts, just not let it run unless a trigger is coming
from elsewhere.
Uwe had the right idea, I just didn't understand it at the time of
that original thread. I've replied to that thread so hopefully we
can finally get this cleared up.
If you could test what Uwe posted in this message that would be great.
https://lore.kernel.org/all/6oyvsvp2erynwu3evulbg6gtdryabeuoo46qzku2grxg3jxptf@jszhnvmj2ffc/
Thanks for the hard work getting me all the info.
Jonathan
> tomin@fedora:~$ ls /sys/bus/iio/devices/trigger*/name
> ls: cannot access '/sys/bus/iio/devices/trigger*/name': No such file or
> directory
> tomin@fedora:~$ ls /sys/bus/iio/devices/iio\:device*/
> '/sys/bus/iio/devices/iio:device0/':
> buffer events in_accel_x_raw
> in_temp_offset name subsystem
> buffer0 firmware_node in_accel_y_raw
> in_temp_raw power trigger
> current_timestamp_clock in_accel_sampling_frequency in_accel_z_raw
> in_temp_scale sampling_frequency_available uevent
> dev in_accel_scale in_mount_matrix label
> scan_elements waiting_for_supplier
>
> '/sys/bus/iio/devices/iio:device1/':
> buffer events in_accel_x_raw
> in_temp_offset name subsystem
> buffer0 firmware_node in_accel_y_raw
> in_temp_raw power trigger
> current_timestamp_clock in_accel_sampling_frequency in_accel_z_raw
> in_temp_scale sampling_frequency_available uevent
> dev in_accel_scale in_mount_matrix label
> scan_elements waiting_for_supplier
> tomin@fedora:~$ ls /sys/bus/iio/devices/iio\:device*/trigger
> '/sys/bus/iio/devices/iio:device0/trigger':
> current_trigger
>
> '/sys/bus/iio/devices/iio:device1/trigger':
> current_trigger
>
>
>
> tomin@fedora:~$ cat /proc/interrupts
> CPU0 CPU1 CPU2 CPU3
> 1: 0 0 72 0 IR-IO-APIC 1-edge
> i8042
> 8: 0 0 0 0 IR-IO-APIC 8-edge
> rtc0
> 9: 10041 0 0 0 IR-IO-APIC 9-fasteoi
> acpi
> 12: 0 6 0 0 IR-IO-APIC 12-edge
> i8042
> 14: 8 0 0 0 IR-IO-APIC 14-fasteoi
> INTC1057:00
> 16: 56 0 0 0 IR-IO-APIC 16-fasteoi
> mmc0, i801_smbus
> 27: 0 0 5167 0 IR-IO-APIC 27-fasteoi
> i2c_designware.1, idma64.1
> 29: 236 0 0 0 IR-IO-APIC 29-fasteoi
> i2c_designware.3, idma64.3
> 31: 0 0 0 0 IR-IO-APIC 31-fasteoi
> i2c_designware.5, idma64.5
> 32: 0 0 0 0 IR-IO-APIC 32-fasteoi
> i2c_designware.6, idma64.6
> 33: 0 4921 0 0 IR-IO-APIC 33-fasteoi
> i2c_designware.4, idma64.4
> 39: 0 0 0 0 IR-IO-APIC 39-fasteoi
> pxa2xx-spi.0, idma64.0
> 40: 0 0 0 0 IR-IO-APIC 40-fasteoi
> i2c_designware.2, idma64.2
> 120: 0 1 0 0 IR-PCI-MSI-0000:00:1d.0
> 0-edge aerdrv, PCIe bwctrl
> 121: 9054 0 0 0 IR-PCI-MSI-0000:00:14.0
> 0-edge xhci_hcd
> 126: 10 4 0 30 IR-PCI-MSIX-0000:01:00.0
> 0-edge nvme0q0
> 127: 7450 0 0 0 IR-PCI-MSIX-0000:01:00.0
> 1-edge nvme0q1
> 128: 0 5690 0 0 IR-PCI-MSIX-0000:01:00.0
> 2-edge nvme0q2
> 129: 0 0 5152 0 IR-PCI-MSIX-0000:01:00.0
> 3-edge nvme0q3
> 130: 0 0 0 6240 IR-PCI-MSIX-0000:01:00.0
> 4-edge nvme0q4
> 131: 0 10732 10690 1008 IR-PCI-MSI-0000:00:02.0
> 0-edge i915
> 132: 8 0 0 0 intel-gpio 306
> GDIX1001:00
> 133: 0 49 0 0 IR-PCI-MSI-0000:00:16.0
> 0-edge mei_me
> 134: 883 1015 400 779 IR-PCI-MSIX-0000:00:14.3
> 0-edge iwlwifi:default_queue
> 135: 46 59 35 4 IR-PCI-MSIX-0000:00:14.3
> 1-edge iwlwifi:queue_1
> 136: 5 68 1 17 IR-PCI-MSIX-0000:00:14.3
> 2-edge iwlwifi:queue_2
> 137: 20 30 25 35 IR-PCI-MSIX-0000:00:14.3
> 3-edge iwlwifi:queue_3
> 138: 21 123 114 269 IR-PCI-MSIX-0000:00:14.3
> 4-edge iwlwifi:queue_4
> 139: 0 0 0 5 IR-PCI-MSIX-0000:00:14.3
> 5-edge iwlwifi:exception
> 140: 1213 0 0 0 IR-PCI-MSI-0000:00:1f.3
> 0-edge snd_hda_intel:card1
> NMI: 8 8 9 8 Non-maskable interrupts
> LOC: 87542 86732 94323 81275 Local timer interrupts
> SPU: 0 0 0 0 Spurious interrupts
> PMI: 8 8 9 8 Performance monitoring
> interrupts
> IWI: 2334 10486 9187 2892 IRQ work interrupts
> RTR: 0 0 0 0 APIC ICR read retries
> RES: 1781 1199 1600 3146 Rescheduling interrupts
> CAL: 23231 22621 16364 21816 Function call interrupts
> TLB: 1208 1127 1072 1304 TLB shootdowns
> TRM: 680 680 680 680 Thermal event interrupts
> THR: 0 0 0 0 Threshold APIC interrupts
> DFR: 0 0 0 0 Deferred Error APIC
> interrupts
> MCE: 0 0 0 0 Machine check exceptions
> MCP: 3 4 4 4 Machine check polls
> ERR: 0
> MIS: 0
> PIN: 0 0 0 0 Posted-interrupt
> notification event
> NPI: 0 0 0 0 Nested posted-interrupt
> event
> PIW: 0 0 0 0 Posted-interrupt wakeup
> event
> PMN: 0 0 0 0 Posted MSI notification
> event
>
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-11-15 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 17:07 [Bug 220772] New: NULL pointer dereference in bmc150-accel-core bugzilla-daemon
2025-11-09 19:59 ` [Bug 220772] " bugzilla-daemon
2025-11-11 20:09 ` Jonathan Cameron
2025-11-11 20:09 ` bugzilla-daemon
2025-11-12 1:46 ` bugzilla-daemon
2025-11-15 18:25 ` Jonathan Cameron
2025-11-15 18:25 ` bugzilla-daemon [this message]
2025-11-16 12:05 ` bugzilla-daemon
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=bug-220772-217253-6YvaYGoAZn@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-iio@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).