linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: masahiroy@kernel.org
Cc: ndesaulniers@google.com, morbo@google.com,
	justinstitt@google.com,  keescook@chromium.org,
	samitolvanen@google.com, nicolas@fjasle.eu,
	 linux-kbuild@vger.kernel.org, llvm@lists.linux.dev,
	patches@lists.linux.dev,  kernel test robot <lkp@intel.com>,
	 Anton Ivanov <anton.ivanov@cambridgegreys.com>,
	 Nathan Chancellor <nathan@kernel.org>,
	richard@nod.at,  johannes@sipsolutions.net,
	linux-um@lists.infradead.org
Subject: [PATCH v2 0/2] Enable -Wincompatible-function-pointer-types-strict under W=1
Date: Wed, 06 Dec 2023 09:49:45 -0700	[thread overview]
Message-ID: <20231206-enable-wincompatible-function-pointer-types-strict-w-1-v2-0-91311b4c37b0@kernel.org> (raw)

-Wincompatible-function-pointer-types-strict is a warning in clang-16
and newer that is designed to catch potential kCFI failures at runtime.
There is one set of warnings in drivers/counter that I have not been
able to figure out a solution for so this cannot be enabled for a
default build but adding the warning under W=1 will allow various CI
systems to catch and report new instances so it will be easier to
enable in a default build in the future.

The kbuild test robot reported one instance in arch/um, which is cleared
up by the first patch and has an ack from an arch/um maintainer, so this
should be able to go in via the kbuild tree.

---
Changes in v2:
- Rebase on latest kbuild tree.
- Pick up Nick's reviewed-by tag.
- Include arch/um patch with Anton's ack to clear up warning reported by
  kbuild test robot on v1.
- Link to v1: https://lore.kernel.org/r/20231002-enable-wincompatible-function-pointer-types-strict-w-1-v1-1-808ab955d42d@kernel.org

---
Nathan Chancellor (2):
      um: net: Fix return type of uml_net_start_xmit()
      kbuild: Enable -Wincompatible-function-pointer-types-strict in W=1

 arch/um/drivers/net_kern.c | 2 +-
 scripts/Makefile.extrawarn | 1 +
 2 files changed, 2 insertions(+), 1 deletion(-)
---
base-commit: 4b391dcb7cda8d1353d3bd123d0989550d48c0c9
change-id: 20231002-enable-wincompatible-function-pointer-types-strict-w-1-4a56b99b8c6f

Best regards,
-- 
Nathan Chancellor <nathan@kernel.org>



             reply	other threads:[~2023-12-06 16:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 16:49 Nathan Chancellor [this message]
2023-12-06 16:49 ` [PATCH v2 1/2] um: net: Fix return type of uml_net_start_xmit() Nathan Chancellor

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=20231206-enable-wincompatible-function-pointer-types-strict-w-1-v2-0-91311b4c37b0@kernel.org \
    --to=nathan@kernel.org \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=johannes@sipsolutions.net \
    --cc=justinstitt@google.com \
    --cc=keescook@chromium.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=morbo@google.com \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    --cc=patches@lists.linux.dev \
    --cc=richard@nod.at \
    --cc=samitolvanen@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).