public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: <linux-kernel@vger.kernel.org>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	David Hildenbrand <david@redhat.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Heiko Carstens <hca@linux.ibm.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Sven Schnelle <svens@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>, <linux-s390@vger.kernel.org>,
	<kvm@vger.kernel.org>
Subject: Re: [PATCH 2/2] lib/bitmap: drop optimization of bitmap_{from,to}_arr64
Date: Tue, 28 Feb 2023 11:45:18 +0100	[thread overview]
Message-ID: <fd0da26f-6437-75bf-c013-f338174325fe@intel.com> (raw)
In-Reply-To: <20230227214524.914050-2-yury.norov@gmail.com>

From: Yury Norov <yury.norov@gmail.com>
Date: Mon, 27 Feb 2023 13:45:24 -0800

> bitmap_{from,to}_arr64() optimization is overly optimistic on 32-bit LE
> architectures when it's wired to bitmap_copy_clear_tail().
> 
> bitmap_copy_clear_tail() takes care of unused bits in the bitmap up to
> the next word boundary. But on 32-bit machines when copying bits from
> bitmap to array of 64-bit words, it's expected that the unused part of
> a recipient array must be cleared up to 64-bit boundary, so the last 4
> bytes may stay untouched when nbits % 64 <= 32.
> 
> While the copying part of the optimization works correct, that clear-tail
> trick makes corresponding tests reasonably fail:
> 
> test_bitmap: bitmap_to_arr64(nbits == 1): tail is not safely cleared: 0xa5a5a5a500000001 (must be 0x0000000000000001)
> 
> Fix it by removing bitmap_{from,to}_arr64() optimization for 32-bit LE
> arches.
> 
> Reported-by: Guenter Roeck <linux@roeck-us.net>
> Link: https://lore.kernel.org/lkml/20230225184702.GA3587246@roeck-us.net/
> Fixes: 0a97953fd221 ("lib: add bitmap_{from,to}_arr64")
> Signed-off-by: Yury Norov <yury.norov@gmail.com>
> Tested-by: Guenter Roeck <linux@roeck-us.net>
> ---
>  include/linux/bitmap.h | 8 +++-----
>  lib/bitmap.c           | 2 +-
>  2 files changed, 4 insertions(+), 6 deletions(-)
> 
> diff --git a/include/linux/bitmap.h b/include/linux/bitmap.h
> index 40e53a2ecc0d..7d4c90eb3df4 100644
> --- a/include/linux/bitmap.h
> +++ b/include/linux/bitmap.h
> @@ -302,12 +302,10 @@ void bitmap_to_arr32(u32 *buf, const unsigned long *bitmap,
>  #endif
>  
>  /*
> - * On 64-bit systems bitmaps are represented as u64 arrays internally. On LE32
> - * machines the order of hi and lo parts of numbers match the bitmap structure.
> - * In both cases conversion is not needed when copying data from/to arrays of
> - * u64.
> + * On 64-bit systems bitmaps are represented as u64 arrays internally. So,
> + * the conversion is not needed when copying data from/to arrays of u64.
>   */
> -#if (BITS_PER_LONG == 32) && defined(__BIG_ENDIAN)
> +#if BITS_PER_LONG == 32
>  void bitmap_from_arr64(unsigned long *bitmap, const u64 *buf, unsigned int nbits);
>  void bitmap_to_arr64(u64 *buf, const unsigned long *bitmap, unsigned int nbits);
>  #else
> diff --git a/lib/bitmap.c b/lib/bitmap.c
> index 1c81413c51f8..ddb31015e38a 100644
> --- a/lib/bitmap.c
> +++ b/lib/bitmap.c
> @@ -1495,7 +1495,7 @@ void bitmap_to_arr32(u32 *buf, const unsigned long *bitmap, unsigned int nbits)
>  EXPORT_SYMBOL(bitmap_to_arr32);
>  #endif
>  
> -#if (BITS_PER_LONG == 32) && defined(__BIG_ENDIAN)
> +#if BITS_PER_LONG == 32
>  /**
>   * bitmap_from_arr64 - copy the contents of u64 array of bits to bitmap
>   *	@bitmap: array of unsigned longs, the destination bitmap

For the series:

Reviewed-by: Alexander Lobakin <aleksander.lobakin@intel.com>

Thanks,
Olek

  reply	other threads:[~2023-02-28 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 21:45 [PATCH 1/2] lib/test_bitmap: increment failure counter properly Yury Norov
2023-02-27 21:45 ` [PATCH 2/2] lib/bitmap: drop optimization of bitmap_{from,to}_arr64 Yury Norov
2023-02-28 10:45   ` Alexander Lobakin [this message]
2023-02-27 22:55 ` [PATCH 1/2] lib/test_bitmap: increment failure counter properly Andy Shevchenko
2023-02-28  2:49   ` Yury Norov
2023-03-01 15:11     ` Andy Shevchenko

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=fd0da26f-6437-75bf-c013-f338174325fe@intel.com \
    --to=aleksander.lobakin@intel.com \
    --cc=agordeev@linux.ibm.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=linux@roeck-us.net \
    --cc=svens@linux.ibm.com \
    --cc=yury.norov@gmail.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