From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Tyler Hicks <code@tyhicks.com>,
Christian Brauner <brauner@kernel.org>,
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
Subject: Re: [PATCH v2 0/3] fs/ecryptfs: Replace kmap{,_atomic}() with kmap_local_page()
Date: Wed, 28 Jun 2023 15:50:30 +0200 [thread overview]
Message-ID: <23780760.ouqheUzb2q@suse> (raw)
In-Reply-To: <20230426172223.8896-1-fmdefrancesco@gmail.com>
On mercoledì 26 aprile 2023 19:22:20 CEST 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().
After two months from submission, I haven't received any comments on this
short series yet, except for a "Reviewed by" tag from Ira on patch 1/3 only.
I would appreciate any comments/reviews/acks and would especially like to know
if anything is preventing these patches from being applied.
Thank you all in advance,
Fabio
> Tested in a QEMU/KVM x86_32 VM, 6GB RAM, booting a kernel with
> HIGHMEM64GB enabled.
>
> v1->v2: Patches 1/3 and 2/3 were not grouped in a series. Patch 3/3 is
> new. Therefore, currently one series groups all conversions needed if
> fs/ecryptfs. The subject of 2/3 changed to differentiate between it and
> 3/3. Furthermore, the commit messages of 1/3 and 2/3 have been largely
> reworked.
>
> Fabio M. De Francesco (3):
> fs/ecryptfs: Replace kmap() with kmap_local_page()
> fs/ecryptfs: Use kmap_local_page() in ecryptfs_write()
> fs/ecryptfs: Use kmap_local_page() in copy_up_encrypted_with_header()
>
> fs/ecryptfs/crypto.c | 8 ++++----
> fs/ecryptfs/mmap.c | 4 ++--
> fs/ecryptfs/read_write.c | 12 ++++++------
> 3 files changed, 12 insertions(+), 12 deletions(-)
>
> --
> 2.40.0
next prev parent reply other threads:[~2023-06-28 13:50 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 ` Fabio M. De Francesco [this message]
2023-06-30 2:31 ` [PATCH v2 0/3] fs/ecryptfs: Replace kmap{,_atomic}() with kmap_local_page() Eric Biggers
2023-06-30 7:38 ` Christian Brauner
2023-06-30 8:45 ` Christian Brauner
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=23780760.ouqheUzb2q@suse \
--to=fmdefrancesco@gmail.com \
--cc=brauner@kernel.org \
--cc=code@tyhicks.com \
--cc=dchinner@redhat.com \
--cc=ecryptfs@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.