public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Wang Yugui <wangyugui@e16-tech.com>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>, Nick Terrell <terrelln@fb.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	Filipe Manana <fdmanana@kernel.org>,
	Ira Weiny <ira.weiny@intel.com>
Subject: Re: [PATCH] btrfs: Replace kmap() with kmap_local_page() in zstd.c
Date: Thu, 14 Jul 2022 09:46:00 +0200	[thread overview]
Message-ID: <8091114.T7Z3S40VBb@opensuse> (raw)
In-Reply-To: <20220714082519.A7C9.409509F4@e16-tech.com>

On giovedì 14 luglio 2022 02:25:20 CEST Wang Yugui wrote:
> Hi,
> 
> Compiler warning:
> 
> fs/btrfs/zstd.c:478:55: warning: passing argument 1 of ‘__kunmap_local’ 
discards ‘const’ qualifier from pointer target type [-Wdiscarded-
qualifiers]
>   478 |                         kunmap_local(workspace->in_buf.src);
> ./include/linux/highmem-internal.h:284:24: note: in definition of macro 
‘kunmap_local’
>   284 |         __kunmap_local(__addr);                                 \
>       |                        ^~~~~~
> ./include/linux/highmem-internal.h:200:41: note: expected ‘void *’ but 
argument is of type ‘const void *’
>   200 | static inline void __kunmap_local(void *addr)
>       |                                   ~~~~~~^~~~
> 
> Best Regards
> Wang Yugui (wangyugui@e16-tech.com)
> 2022/07/14

Thanks for the build test, but you're a little late :)

This patch is superseded by a series of two: please see
[PATCH v6 0/2] btrfs: Replace kmap() with kmap_local_page() in zstd.c
at https://lore.kernel.org/lkml/20220706111520.12858-1-fmdefrancesco@gmail.com/

In that series, patch 1/2 changes __kunmap_{local,atomic}() prototypes to 
take pointers to const void.

Regards,

Fabio

> > The use of kmap() is being deprecated in favor of kmap_local_page(). 
With
> > kmap_local_page(), the mapping is per thread, CPU local and not 
globally
> > visible.
> > 
> > Therefore, use kmap_local_page() / kunmap_local() in zstd.c because in
> > this file the mappings are per thread and are not visible in other
> > contexts; meanwhile refactor zstd_compress_pages() to comply with 
nested
> > local mapping / unmapping ordering rules.
> > 



  reply	other threads:[~2022-07-14  7:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11 13:52 [PATCH] btrfs: Replace kmap() with kmap_local_page() in zstd.c Fabio M. De Francesco
2022-06-13 18:39 ` David Sterba
2022-06-13 23:22   ` Fabio M. De Francesco
2022-06-13 23:42     ` Fabio M. De Francesco
2022-06-14 14:25     ` David Sterba
2022-06-14 16:28       ` Fabio M. De Francesco
2022-06-14 17:07         ` Ira Weiny
2022-06-15  5:29           ` Fabio M. De Francesco
2022-06-15 13:27           ` David Sterba
2022-06-15 13:32           ` David Sterba
2022-07-14  0:25 ` Wang Yugui
2022-07-14  7:46   ` Fabio M. De Francesco [this message]
2022-07-14 12:33   ` David Sterba

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=8091114.T7Z3S40VBb@opensuse \
    --to=fmdefrancesco@gmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=fdmanana@kernel.org \
    --cc=ira.weiny@intel.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=terrelln@fb.com \
    --cc=wangyugui@e16-tech.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