All of
 help / color / mirror / Atom feed
From: Nathan Chancellor <>
Cc:,,,,,,,,,  kernel test robot <>,
	 Anton Ivanov <>,
	 Nathan Chancellor <>,,,
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: <> (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:

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 <>

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

Thread overview: 5+ 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
2023-12-06 20:30   ` Kees Cook
2023-12-06 16:49 ` [PATCH v2 2/2] kbuild: Enable -Wincompatible-function-pointer-types-strict in W=1 Nathan Chancellor
2023-12-06 20:31   ` Kees Cook

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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.