From: Janne Grunau <j@jannau.net>
To: Dmitry Sinyavin <sinyavin@gmail.com>
Cc: Srinivas Kandagatla <srini@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dmitry Baryshkov <lumag@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmem: core: Fix OOB read for bit offsets of more than one byte
Date: Sun, 20 Sep 2026 18:33:49 +0200 [thread overview]
Message-ID: <20260920163349.GA378504@robin.jannau.net> (raw)
In-Reply-To: <20260919185636.3054303-1-sinyavin@gmail.com>
On Sat, Sep 19, 2026 at 08:56:36PM +0200, Dmitry Sinyavin wrote:
> Hi Janne,
>
> Thanks for the patch. I independently ran into this bug while testing
> Qualcomm MDM9607 TSENS calibration. I tested the exact change against the
> current NVMEM for-fixes branch at cee9395acd80.
>
> Without the patch, a focused KUnit case with a 26-bit offset returned the
> expected value but produced three KASAN out-of-bounds reports. On the
> MF283V, the unmodified kernel produced exactly seven reports from four
> TSENS calibration cells, matching the accesses predicted from their bit
> offsets.
>
> With the patch, the focused test and a 16,384-case extraction matrix pass
> under KASAN. A hardware A/B test using otherwise identical Linux 6.18.44
> kernels produced no KASAN report with the fix, and all five TSENS zones
> reported plausible temperatures between 36 and 38 degrees Celsius.
>
> Tested-by: Dmitry Sinyavin <sinyavin@gmail.com>
>
> I could not find the patch in the current NVMEM for-fixes or for-next
> branches. Are you planning to send a v2 with the stable Cc requested in
> the earlier reply? I can send the KUnit coverage separately if useful.
The change is no longer relevant on the systems I discovered the issue
so it got lost and I never sent a v2.
I'll do that shortly with both issues (missing Cc: and long partial
SHA1) fixed and your Tested-by:.
Thanks,
Janne
next prev parent reply other threads:[~2026-09-20 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 7:29 Janne Grunau
2025-09-01 7:40 ` Greg Kroah-Hartman
2026-09-19 18:56 ` Dmitry Sinyavin
2026-09-20 16:33 ` Janne Grunau [this message]
2026-09-20 16:19 ` Srinivas Kandagatla
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=20260920163349.GA378504@robin.jannau.net \
--to=j@jannau.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=sinyavin@gmail.com \
--cc=srini@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
all inboxes | Powered by JetHome®