From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Farhad Alemi <farhad.alemi@berkeley.edu>
Cc: Mark Brown <broonie@kernel.org>, Farhad Alemi <falemi@asu.edu>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] UBSAN: shift-out-of-bounds in dln2_spi_probe
Date: Thu, 10 Sep 2026 09:36:38 +0300 [thread overview]
Message-ID: <aqJP9pVjpLCcp_XA@ashevche-desk.local> (raw)
In-Reply-To: <CA+0ovCioY634b646jDcs2cFmg_1q2UMN4wuTQ1V26Gy+Dm_c+A@mail.gmail.com>
On Wed, Sep 09, 2026 at 05:33:20PM -0700, Farhad Alemi wrote:
> We are reporting the following crash (reproducer and a proposed patch attached):
Thank you.
Please, submit the patch as a formal fix. You can find the necessary steps in
the Submitting Patches documentation.
> Linux version 7.3.0-rc2 50d05c7c76c96b90462f24debacca971d2e86713
> Build Config: UpstreamAppArmorKASAN (KASAN + UBSAN, panic_on_warn=1)
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-09-10 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 0:33 [BUG] UBSAN: shift-out-of-bounds in dln2_spi_probe Farhad Alemi
2026-09-10 6:36 ` Andy Shevchenko [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=aqJP9pVjpLCcp_XA@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=falemi@asu.edu \
--cc=farhad.alemi@berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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