From: Greg KH <gregkh@linuxfoundation.org>
To: Farhad Alemi <farhad.alemi@berkeley.edu>
Cc: Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
falemi@asu.edu, dm-devel@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] UBSAN: shift-out-of-bounds in dm_integrity_map
Date: Fri, 28 Aug 2026 08:02:52 +0200 [thread overview]
Message-ID: <2026082856-unviable-stature-8c04@gregkh> (raw)
In-Reply-To: <CA+0ovCjSR_YcGORgj8Ydab6HtzJDxjOHZx9OU1L8j0PC-KSXmw@mail.gmail.com>
On Thu, Aug 27, 2026 at 10:51:35PM -0700, Farhad Alemi wrote:
> Hello,
>
> As part of the kernel research at ASU's SEFCOM
> lab, we hit the crash below. Crash reports can be found here:
>
> https://github.com/farhad-alemi/public_bug_reports/tree/main/193-ubsan-shift-out-of-bounds-in-dm-integrity-map/
>
> UBSAN: shift-out-of-bounds in drivers/md/dm-integrity.c:2106:52
> shift exponent 138 is too large for 32-bit type 'unsigned int'
> Call Trace:
> dm_integrity_map+0xe14/0xfe0 drivers/md/dm-integrity.c:2106
> __map_bio+0x5e8/0xa60 drivers/md/dm.c:1426
> __split_and_process_bio drivers/md/dm.c:1760 [inline]
> dm_split_and_process_bio drivers/md/dm.c:2034 [inline]
> dm_submit_bio+0x73f/0x2900 drivers/md/dm.c:2090
> __submit_bio+0x475/0x880 block/blk-core.c:644
> submit_bio_noacct_nocheck+0x467/0x990 block/blk-core.c:755
> __block_write_full_folio+0x7ee/0xdc0 fs/buffer.c:1830
> blkdev_writepages+0xef/0x1b0 block/fops.c:486
> Kernel panic - not syncing: UBSAN: panic_on_warn set ...
>
> Our reproducer.c is available upon request.
>
> Happy to test a patch if that would help.
You seem to have sent 59 emails like this in a day....
Please slow down, learn the proper process here, before flooding
different substems with random reports like this that are not helpful at
all.
greg k-h
prev parent reply other threads:[~2026-08-28 6:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 5:51 Farhad Alemi
2026-08-28 6:02 ` Greg KH [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=2026082856-unviable-stature-8c04@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=falemi@asu.edu \
--cc=farhad.alemi@berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@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®