From: Andrew Morton <akpm@linux-foundation.org>
To: "Christian A. Ehrhardt" <lk@c--e.de>
Cc: linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>,
Kees Cook <kees@kernel.org>, Petr Mladek <pmladek@suse.com>,
David Gow <davidgow@google.com>
Subject: Re: [PATCH RESEND 3/3] lib: Fix length calculation in extract_kvec_to_sg
Date: Tue, 24 Mar 2026 12:12:24 -0700 [thread overview]
Message-ID: <20260324121224.c7efad04eafeead81aead946@linux-foundation.org> (raw)
In-Reply-To: <20260323212350.807118-4-lk@c--e.de>
On Mon, 23 Mar 2026 22:23:50 +0100 "Christian A. Ehrhardt" <lk@c--e.de> wrote:
> When extracting from a kvec to a scatterlist, do not
> cross page boundaries. The required length is already
> calculated but not used as intended.
>
> The previous changes to the kunit_iov_iter.c demonstrate
> that the patch is necessary.
Thanks.
> Cc: David Howells <dhowells@redhat.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: stable@vger.kernel.org # v6.5+
Could we please have a description of the userspace-visible impact? To
help others understand why we're proposing a backport,
> --- a/lib/scatterlist.c
> +++ b/lib/scatterlist.c
> @@ -1249,7 +1249,7 @@ static ssize_t extract_kvec_to_sg(struct iov_iter *iter,
> else
> page = virt_to_page((void *)kaddr);
>
> - sg_set_page(sg, page, len, off);
> + sg_set_page(sg, page, seg, off);
> sgtable->nents++;
> sg++;
> sg_max--;
I'm thinking the series should be split up - this patch for 7.0-rcX and
-stable, the kunit changes for 7.0-rcX. Or do you think we should
-stableize the kunit changes also?
Or we put it all into 7.0-rcX and let the -stable patch trickle back
later on. After all, 018584697533 was a couple of years ago. It's hard
to decide on these things without that userspace-visible impact thing!
next prev parent reply other threads:[~2026-03-24 19:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 21:23 [PATCH RESEND 0/3] Fix length calculation bug " Christian A. Ehrhardt
2026-03-23 21:23 ` [PATCH RESEND 1/3] lib: kunit_iov_iter: Improve error detection Christian A. Ehrhardt
2026-03-23 21:23 ` [PATCH RESEND 2/3] lib: kunit_iov_iter: Add tests for extract_iter_to_sg Christian A. Ehrhardt
2026-03-23 21:23 ` [PATCH RESEND 3/3] lib: Fix length calculation in extract_kvec_to_sg Christian A. Ehrhardt
2026-03-24 19:12 ` Andrew Morton [this message]
2026-03-24 19:39 ` Christian A. Ehrhardt
2026-03-24 19:15 ` Andrew Morton
2026-03-24 19:47 ` Christian A. Ehrhardt
2026-03-24 20:08 ` Andrew Morton
2026-03-24 0:03 ` [PATCH RESEND 0/3] Fix length calculation bug " Josh Law
2026-03-24 16:38 ` Josh Law
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=20260324121224.c7efad04eafeead81aead946@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davidgow@google.com \
--cc=dhowells@redhat.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@c--e.de \
--cc=pmladek@suse.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
all inboxes | Powered by JetHome®