Archive-only list for syzbot
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci3a4848f45a900f67@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: mm/filemap: Implement fast short reads
Date: Fri, 17 Oct 2025 08:07:30 -0700	[thread overview]
Message-ID: <68f25bb2.a70a0220.b3ac9.002f.GAE@google.com> (raw)

syzbot ci has tested the following series

[v1] mm/filemap: Implement fast short reads
https://lore.kernel.org/all/20251017141536.577466-1-kirill@shutemov.name
* [PATCH] mm/filemap: Implement fast short reads

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/e07b41fe-ccd9-465e-99d9-69182dbc5c58

***

kernel build error

tree:      torvalds
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base:      3a8660878839faadb4f1a6dd72c3179c1df56787
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/e9ca4b95-c32d-4961-bf73-acd33194de3a/config

fs/inode.c:486:28: error: member reference type 'struct xarray' is not a pointer; did you mean to use '.'?
fs/inode.c:486:11: error: cannot take the address of an rvalue of type 'spinlock_t' (aka 'struct spinlock')

***

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:
[akpm@linux-foundation.org brauner@kernel.org david@redhat.com jack@suse.cz kas@kernel.org kirill@shutemov.name linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org linux-mm@kvack.org torvalds@linux-foundation.org viro@zeniv.linux.org.uk willy@infradead.org]

If the report looks fine to you, reply with:
#syz upstream


                 reply	other threads:[~2025-10-17 15:07 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=68f25bb2.a70a0220.b3ac9.002f.GAE@google.com \
    --to=syzbot+ci3a4848f45a900f67@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox