From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [git pull] build fix
Date: Sat, 11 Jun 2022 20:35:09 +0000 [thread overview]
Message-ID: <YqT8fYe1PqP9rCRs@zeniv-ca.linux.org.uk> (raw)
The following changes since commit 6c77676645ad42993e0a8bdb8dafa517851a352a:
iov_iter: Fix iter_xarray_get_pages{,_alloc}() (2022-06-10 15:56:32 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-fixes
for you to fetch changes up to 5632561eee9faa6d8d9f69bf69d083f1847d1abd:
fix warnings on 32bit caused by ITER_XARRAY fix (2022-06-11 12:43:21 -0400)
----------------------------------------------------------------
minimal fix for build breakage on 32bit
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----------------------------------------------------------------
There's a bunch of obvious cleanups and improvements in that area; this is
just the braino fix for previous commit. I wanted to include at least
replacement of weird open-coded count = DIV_ROUND_UP(size + offset, PAGE_SIZE);
in those two functions (it might have started as defense against theoretical
overflows, but if so it's incomplete, the overflows are in practice impossible
*and* this prevention would be in the wrong place anyway), but... let's
keep that separate.
FWIW, in my local tree duplication between iov_iter_get_pages() and
iov_iter_get_pages_alloc() is gone, with a lot of stuff getting considerably
simpler, but I'm still cleaning/reordering/carving that series up. Will post
tomorrow or on Monday, but those are clearly not 5.19 fodder.
Al Viro (1):
fix warnings on 32bit caused by ITER_XARRAY fix
lib/iov_iter.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
next reply other threads:[~2022-06-11 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 20:35 Al Viro [this message]
2022-06-11 20:54 ` Linus Torvalds
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=YqT8fYe1PqP9rCRs@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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®