mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Yury Norov <yury.norov@gmail.com>
Cc: Kees Cook <keescook@chromium.org>,
	Christophe de Dinechin <dinechin@redhat.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Zhen Lei <thunder.leizhen@huawei.com>,
	linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: [PATCH v3 0/2] bitmap: Fix return values to be unsigned
Date: Wed, 18 May 2022 13:52:21 -0700	[thread overview]
Message-ID: <20220518205223.2908736-1-keescook@chromium.org> (raw)

Hi,

v1: https://lore.kernel.org/lkml/20220517035411.31144-1-keescook@chromium.org
v2: https://lore.kernel.org/lkml/20220517212234.868181-1-keescook@chromium.org
v3:
 - Update missed int variable to unsigned int
 - Update tools/ bitmaps code to match
 - Adjust whitespace a bit

Rationale repeated from the last patch:

Both nodemask and bitmap routines had mixed return values that provided
potentially signed results that could never happen. This was leading to
the compiler getting confusing about the range of possible return values
(it was thinking things could be negative where they could not be). Fix
all the nodemask and bitmap routines that should be returning unsigned
(or bool) values. Silences GCC 12 warnings:

 mm/swapfile.c: In function ‘setup_swap_info’:
 mm/swapfile.c:2291:47: error: array subscript -1 is below array bounds of ‘struct plist_node[]’ [-Werror=array-bounds]
  2291 |                                 p->avail_lists[i].prio = 1;
       |                                 ~~~~~~~~~~~~~~^~~
 In file included from mm/swapfile.c:16:
 ./include/linux/swap.h:292:27: note: while referencing ‘avail_lists’
   292 |         struct plist_node avail_lists[]; /*
       |                           ^~~~~~~~~~~


I note that Alexey and Rasmus have touched on this area in the past,
fixing up node ids to be unsigned:

ce0725f78a56 ("numa: make "nr_online_nodes" unsigned int")
b9726c26dc21 ("numa: make "nr_node_ids" unsigned int")
33c4fa8c6763 ("linux/nodemask.h: update bitmap wrappers to take unsigned int")

-Kees


Kees Cook (2):
  bitmap: Fix return values to be unsigned
  nodemask: Fix return values to be unsigned

 include/linux/bitmap.h       | 25 ++++++++++++------------
 include/linux/nodemask.h     | 38 ++++++++++++++++++------------------
 lib/bitmap.c                 | 30 ++++++++++++++--------------
 lib/nodemask.c               |  4 ++--
 tools/include/linux/bitmap.h | 17 ++++++++--------
 tools/lib/bitmap.c           | 20 +++++++++----------
 6 files changed, 68 insertions(+), 66 deletions(-)

-- 
2.32.0


             reply	other threads:[~2022-05-18 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 20:52 Kees Cook [this message]
2022-05-18 20:52 ` [PATCH v3 1/2] " Kees Cook
2022-05-18 20:52 ` [PATCH v3 2/2] nodemask: " Kees Cook
2022-05-18 21:55 ` [PATCH v3 0/2] bitmap: " Yury Norov

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=20220518205223.2908736-1-keescook@chromium.org \
    --to=keescook@chromium.org \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dinechin@redhat.com \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=thunder.leizhen@huawei.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

all inboxes | Powered by JetHome®