From: syzbot ci <syzbot+cic233d0fef33be460@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: dm-crypt: allow unaligned bio_vecs for direct io
Date: Thu, 18 Sep 2025 11:33:24 -0700 [thread overview]
Message-ID: <68cc5074.050a0220.28a605.000b.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] dm-crypt: allow unaligned bio_vecs for direct io
https://lore.kernel.org/all/20250918161642.2867886-1-kbusch@meta.com
* [RFC PATCH] dm-crypt: allow unaligned bio_vecs for direct io
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/613aac3a-6ac5-422a-86a4-c1f0b6845e2a
***
kernel build error
tree: torvalds
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base: f83ec76bf285bea5727f478a68b894f5543ca76e
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/6441f6d0-523e-471e-9aa7-706d3367f153/config
drivers/md/dm-crypt.c:1473:8: error: assigning to 'struct scatterlist *' from incompatible type 'struct scatterlist'; take the address with &
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
The email will later be sent to:
[dm-devel@lists.linux.dev ebiggers@google.com kbusch@kernel.org kbusch@meta.com linux-block@vger.kernel.org mpatocka@redhat.com snitzer@kernel.org]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-09-18 18:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=68cc5074.050a0220.28a605.000b.GAE@google.com \
--to=syzbot+cic233d0fef33be460@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.