public inbox for syzbot@lists.linux.dev
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci9c12c63dd6fe3f46@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: netfs: [WIP] Keep track of folios in a segmented bio_vec[] chain
Date: Thu, 05 Mar 2026 01:00:39 -0800	[thread overview]
Message-ID: <69a94637.a70a0220.2f119.0005.GAE@google.com> (raw)

syzbot ci has tested the following series

[v1] netfs: [WIP] Keep track of folios in a segmented bio_vec[] chain
https://lore.kernel.org/all/20260304140328.112636-1-dhowells@redhat.com
* [RFC PATCH 01/17] netfs: Fix unbuffered/DIO writes to dispatch subrequests in strict sequence
* [RFC PATCH 02/17] vfs: Implement a FIEMAP callback
* [RFC PATCH 03/17] iov_iter: Add a segmented queue of bio_vec[]
* [RFC PATCH 04/17] Add a function to kmap one page of a multipage bio_vec
* [RFC PATCH 05/17] netfs: Add some tools for managing bvecq chains
* [RFC PATCH 06/17] afs: Use a bvecq to hold dir content rather than folioq
* [RFC PATCH 07/17] netfs: Add a function to extract from an iter into a bvecq
* [RFC PATCH 08/17] cifs: Use a bvecq for buffering instead of a folioq
* [RFC PATCH 09/17] cifs: Support ITER_BVECQ in smb_extract_iter_to_rdma()
* [RFC PATCH 10/17] netfs: Switch to using bvecq rather than folio_queue and rolling_buffer
* [RFC PATCH 11/17] cifs: Remove support for ITER_KVEC/BVEC/FOLIOQ from smb_extract_iter_to_rdma()
* [RFC PATCH 12/17] netfs: Remove netfs_alloc/free_folioq_buffer()
* [RFC PATCH 13/17] netfs: Remove netfs_extract_user_iter()
* [RFC PATCH 14/17] iov_iter: Remove ITER_FOLIOQ
* [RFC PATCH 15/17] netfs: Remove folio_queue and rolling_buffer
* [RFC PATCH 16/17] netfs: Check for too much data being read
* [RFC PATCH 17/17] netfs: Combine prepare and issue ops and grab the buffers on request

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/34bae306-6b8c-4cb3-9042-755ab205d7ae

***

kernel build error

tree:      torvalds
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux
base:      24d87712727a5017ad142d63940589a36cd25647
arch:      amd64
compiler:  Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
config:    https://ci.syzbot.org/builds/d4138731-3994-4f14-bc07-1d9fd8386559/config

fs/nfs/fscache.c:275:12: error: use of undeclared identifier 'NETFS_RREQ_USE_PGPRIV2'
fs/nfs/fscache.c:276:22: error: no member named 'sreq_max_len' in 'struct netfs_io_stream'

***

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:
[axboe@kernel.dk ceph-devel@vger.kernel.org christian@brauner.io chuck.lever@oracle.com dhowells@redhat.com hch@infradead.org leon@kernel.org linkinjeon@kernel.org linux-afs@lists.infradead.org linux-block@vger.kernel.org linux-cifs@vger.kernel.org linux-fsdevel@vger.kernel.org linux-kernel@vger.kernel.org linux-nfs@vger.kernel.org marc.dionne@auristor.com netfs@lists.linux.dev pc@manguebit.com pc@manguebit.org sfrench@samba.org sprasad@microsoft.com tom@talpey.com v9fs@lists.linux.dev willy@infradead.org]

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

If the report is a false positive, reply with
#syz invalid


                 reply	other threads:[~2026-03-05  9:00 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=69a94637.a70a0220.2f119.0005.GAE@google.com \
    --to=syzbot+ci9c12c63dd6fe3f46@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