From: Christian Brauner <brauner@kernel.org>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
Tyler Hicks <code@tyhicks.com>,
Dave Chinner <dchinner@redhat.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Al Viro <viro@zeniv.linux.org.uk>,
ecryptfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Eric Biggers <ebiggers@kernel.org>
Subject: Re: [PATCH v2 0/3] fs/ecryptfs: Replace kmap{,_atomic}() with kmap_local_page()
Date: Fri, 30 Jun 2023 10:45:17 +0200 [thread overview]
Message-ID: <20230630-umfang-pumpt-a0cd2d6cdd91@brauner> (raw)
In-Reply-To: <20230426172223.8896-1-fmdefrancesco@gmail.com>
On Wed, 26 Apr 2023 19:22:20 +0200, Fabio M. De Francesco wrote:
> kmap() and kmap_atomic() have been deprecated in favor of
> kmap_local_page().
>
> Therefore, replace kmap() and kmap_atomic() with kmap_local_page().
>
> Tested in a QEMU/KVM x86_32 VM, 6GB RAM, booting a kernel with
> HIGHMEM64GB enabled.
>
> [...]
Picking this up. Please tell me if this should be routed somewhere else.
vfs.misc will be rebased once v6.5-rc1 is released.
---
Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/3] fs/ecryptfs: Replace kmap() with kmap_local_page()
https://git.kernel.org/vfs/vfs/c/7a367455b6a5
[2/3] fs/ecryptfs: Use kmap_local_page() in ecryptfs_write()
https://git.kernel.org/vfs/vfs/c/55f13011af9d
[3/3] fs/ecryptfs: Use kmap_local_page() in copy_up_encrypted_with_header()
https://git.kernel.org/vfs/vfs/c/de9f5a15080f
next prev parent reply other threads:[~2023-06-30 8:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 17:22 [PATCH v2 0/3] fs/ecryptfs: Replace kmap{,_atomic}() with kmap_local_page() Fabio M. De Francesco
2023-04-26 17:22 ` [PATCH v2 1/3] fs/ecryptfs: Replace kmap() " Fabio M. De Francesco
2023-04-26 17:22 ` [PATCH v2 2/3] fs/ecryptfs: Use kmap_local_page() in ecryptfs_write() Fabio M. De Francesco
2023-04-26 17:22 ` [PATCH v2 3/3] fs/ecryptfs: Use kmap_local_page() in copy_up_encrypted_with_header() Fabio M. De Francesco
2023-06-28 13:50 ` [PATCH v2 0/3] fs/ecryptfs: Replace kmap{,_atomic}() with kmap_local_page() Fabio M. De Francesco
2023-06-30 2:31 ` Eric Biggers
2023-06-30 7:38 ` Christian Brauner
2023-06-30 8:45 ` Christian Brauner [this message]
2023-07-01 10:46 ` Fabio M. De Francesco
2023-08-17 17:13 ` Fabio M. De Francesco
2023-08-18 13:18 ` Christian Brauner
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=20230630-umfang-pumpt-a0cd2d6cdd91@brauner \
--to=brauner@kernel.org \
--cc=code@tyhicks.com \
--cc=dchinner@redhat.com \
--cc=ebiggers@kernel.org \
--cc=ecryptfs@vger.kernel.org \
--cc=fmdefrancesco@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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