From: bugzilla-daemon@kernel.org
To: linux-iio@vger.kernel.org
Subject: [Bug 220772] NULL pointer dereference in bmc150-accel-core
Date: Tue, 11 Nov 2025 20:09:31 +0000 [thread overview]
Message-ID: <bug-220772-217253-6scLnwUP5Z@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 #2 from Jonathan Cameron (jic23@kernel.org) ---
On Sun, 09 Nov 2025 19:59:38 +0000
bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=220772
>
> Alon Ohana (alon4dota2@gmail.com) changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |alon4dota2@gmail.com
>
> --- Comment #1 from Alon Ohana (alon4dota2@gmail.com) ---
> Created attachment 308926
> --> https://bugzilla.kernel.org/attachment.cgi?id=308926&action=edit
> bmc150_accel_buffer_postenable NULL deref diff
>
Thanks for the report. The thread you reference does discuss
the correct fix. The ability to enable interrupts at all should be
prevented by removing the userspace interfaces (that are misleading
if there is no interrupt available!).
A few oddities that didn't come up in that thread though.
The trigger provided by this device is not registered if irq <= 0
So we must be using some other trigger or something else is going on.
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
--
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-11 20:09 UTC|newest]
Thread overview: 5+ 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 [this message]
2025-11-12 1:46 ` 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-6scLnwUP5Z@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).