All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Justin Stitt <justinstitt@google.com>,
	James Morse <james.morse@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Oliver Upton <oliver.upton@linux.dev>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Tom Rix <trix@redhat.com>,
	linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
	stable@vger.kernel.org
Subject: Re: [PATCH 6.1.y] KVM: arm64: silence -Wuninitialized-const-pointer warning
Date: Fri, 25 Jul 2025 17:53:19 +0100	[thread overview]
Message-ID: <86bjp88b5s.wl-maz@kernel.org> (raw)
In-Reply-To: <20250725162654.GA684490@ax162>

On Fri, 25 Jul 2025 17:26:54 +0100,
Nathan Chancellor <nathan@kernel.org> wrote:
> 
> On Fri, Jul 25, 2025 at 08:30:21AM +0100, Marc Zyngier wrote:
> > The correct fix would be to backport the series described in
> > e8789ab7047a8, which should be easy enough to apply. it would also
> > make 6.1 less of a terrible kernel.
> 
> If doing that is reasonable to clear this up, I think that would be fine
> to do. This is the only stable-only instance of that warning that I have
> seen in the build logs, I have sent patches to deal with all the other
> instances upstream. We would need this in 5.15 to avoid failures from
> -Werror as well but if it is too hard to backport that series there, we
> could just disable this warning for this file since we know it is a
> false positive.

5.15 would be rather challenging, I'm afraid, and I wouldn't want to
review such a thing.

> The whole reason the warning occurs is due to the constness of the
> sys_reg_desc parameter in the function created by FUNCTION_INVARIANT(),
> which I am guessing cannot be removed because it is present in
> ->access() and it proliferates out from there?

Exactly. Which was a rather bad move when it was introduced over a
decade ago (in v3.11), and we only got 'round to killing it entirely
in v6.15.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

  reply	other threads:[~2025-07-25 16:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25  1:15 [PATCH 6.1.y] KVM: arm64: silence -Wuninitialized-const-pointer warning Justin Stitt
2025-07-25  1:19 ` Justin Stitt
2025-07-25  7:30 ` Marc Zyngier
2025-07-25 16:26   ` Nathan Chancellor
2025-07-25 16:53     ` Marc Zyngier [this message]
2025-07-25  8:58 ` Greg KH
2025-07-25 16:38   ` Nathan Chancellor
2025-07-25 17:08     ` Greg KH
2025-07-26  1:01 ` Sasha Levin

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=86bjp88b5s.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=alexandru.elisei@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=justinstitt@google.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=trix@redhat.com \
    --cc=will@kernel.org \
    /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 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.