From: Vitaly Chikunov <vt@altlinux.org>
To: Deepanshu Kartikey <kartikey406@gmail.com>
Cc: dhowells@redhat.com, pc@manguebit.org, jlayton@kernel.org,
netfs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+9c058f0d63475adc97fd@syzkaller.appspotmail.com
Subject: Re: [PATCH] netfs: Fix kernel BUG in netfs_limit_iter() for ITER_KVEC iterators
Date: Fri, 13 Mar 2026 18:14:54 +0300 [thread overview]
Message-ID: <abQoe8YqMc-xa8KA@altlinux.org> (raw)
In-Reply-To: <20260307090041.359870-1-kartikey406@gmail.com>
Deepanshu, David,
On Sat, Mar 07, 2026 at 02:30:41PM +0530, Deepanshu Kartikey wrote:
> When a process crashes and the kernel writes a core dump to a 9P
> filesystem, __kernel_write() creates an ITER_KVEC iterator. This
> iterator reaches netfs_limit_iter() via netfs_unbuffered_write(), which
> only handles ITER_FOLIOQ, ITER_BVEC and ITER_XARRAY iterator types,
> hitting the BUG() for any other type.
>
> Fix this by adding netfs_limit_kvec() following the same pattern as
> netfs_limit_bvec(), since both kvec and bvec are simple segment arrays
> with pointer and length fields. Dispatch it from netfs_limit_iter() when
> the iterator type is ITER_KVEC.
[ 1.901035] kernel BUG at fs/netfs/iterator.c:248!
We hit the issue in v6.18.17 and the patch resolved it.
Tested-by: Vitaly Chikunov <vt@altlinux.org>
Thanks,
>
> Fixes: cae932d3aee5 ("netfs: Add func to calculate pagecount/size-limited span of an iterator")
> Reported-by: syzbot+9c058f0d63475adc97fd@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=9c058f0d63475adc97fd
> Tested-by: syzbot+9c058f0d63475adc97fd@syzkaller.appspotmail.com
> Signed-off-by: Deepanshu Kartikey <Kartikey406@gmail.com>
> ---
> fs/netfs/iterator.c | 43 +++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 43 insertions(+)
>
> diff --git a/fs/netfs/iterator.c b/fs/netfs/iterator.c
> index 72a435e5fc6d..154a14bb2d7f 100644
> --- a/fs/netfs/iterator.c
> +++ b/fs/netfs/iterator.c
> @@ -142,6 +142,47 @@ static size_t netfs_limit_bvec(const struct iov_iter *iter, size_t start_offset,
> return min(span, max_size);
> }
>
> +/*
> + * Select the span of a kvec iterator we're going to use. Limit it by both
> + * maximum size and maximum number of segments. Returns the size of the span
> + * in bytes.
> + */
> +static size_t netfs_limit_kvec(const struct iov_iter *iter, size_t start_offset,
> + size_t max_size, size_t max_segs)
> +{
> + const struct kvec *kvecs = iter->kvec;
> + unsigned int nkv = iter->nr_segs, ix = 0, nsegs = 0;
> + size_t len, span = 0, n = iter->count;
> + size_t skip = iter->iov_offset + start_offset;
> +
> + if (WARN_ON(!iov_iter_is_kvec(iter)) ||
> + WARN_ON(start_offset > n) ||
> + n == 0)
> + return 0;
> +
> + while (n && ix < nkv && skip) {
> + len = kvecs[ix].iov_len;
> + if (skip < len)
> + break;
> + skip -= len;
> + n -= len;
> + ix++;
> + }
> +
> + while (n && ix < nkv) {
> + len = min3(n, kvecs[ix].iov_len - skip, max_size);
> + span += len;
> + nsegs++;
> + ix++;
> + if (span >= max_size || nsegs >= max_segs)
> + break;
> + skip = 0;
> + n -= len;
> + }
> +
> + return min(span, max_size);
> +}
> +
> /*
> * Select the span of an xarray iterator we're going to use. Limit it by both
> * maximum size and maximum number of segments. It is assumed that segments
> @@ -245,6 +286,8 @@ size_t netfs_limit_iter(const struct iov_iter *iter, size_t start_offset,
> return netfs_limit_bvec(iter, start_offset, max_size, max_segs);
> if (iov_iter_is_xarray(iter))
> return netfs_limit_xarray(iter, start_offset, max_size, max_segs);
> + if (iov_iter_is_kvec(iter))
> + return netfs_limit_kvec(iter, start_offset, max_size, max_segs);
> BUG();
> }
> EXPORT_SYMBOL(netfs_limit_iter);
> --
> 2.43.0
>
prev parent reply other threads:[~2026-03-13 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 9:00 [PATCH] netfs: Fix kernel BUG in netfs_limit_iter() for ITER_KVEC iterators Deepanshu Kartikey
2026-03-07 13:51 ` David Howells
2026-03-09 9:17 ` Christian Brauner
2026-03-13 15:14 ` Vitaly Chikunov [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=abQoe8YqMc-xa8KA@altlinux.org \
--to=vt@altlinux.org \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=kartikey406@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netfs@lists.linux.dev \
--cc=pc@manguebit.org \
--cc=syzbot+9c058f0d63475adc97fd@syzkaller.appspotmail.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