From: Greg KH <gregkh@linuxfoundation.org>
To: Shreenidhi Shedi <yesshedi@gmail.com>
Cc: acme@kernel.org, linux@treblig.org, mikhail.v.gavrilov@gmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH 6.1.y v2 00/18] Backport fixes for -Wdiscarded-qualifiers and -Wnonnull with newer glibc
Date: Wed, 13 May 2026 09:21:20 +0200 [thread overview]
Message-ID: <2026051315-engorge-agreed-39cb@gregkh> (raw)
In-Reply-To: <369f39de-e013-4b60-9b24-831a72af4ff6@gmail.com>
On Wed, May 13, 2026 at 12:07:30PM +0530, Shreenidhi Shedi wrote:
> On 11/05/26 13:46, Greg KH wrote:
> > On Mon, May 11, 2026 at 12:40:33PM +0530, Shreenidhi Shedi wrote:
> > > Hi all,
> > >
> > > This patch series backports a number of patches from master to 6.1.y
> > > to fix `-Wdiscarded-qualifiers` and `-Wnonnull` build issues with
> > > newer glibc versions.
> > >
> > > I will port these changes to other stable trees once this gets reviewed.
> >
> > You need to do this first for newer kernel trees, and only if they are
> > accepted there, should you do this for older ones as you do not want to
> > have regressions moving to newer kernels, right?
> >
> > But first, why do this at all? You should always be using the latest
> > kernel version of perf on older kernels, especially if you are updating
> > glibc.
> >
> > And if you update glibc, WHY ARE YOU NOT UPDATING YOUR KERNEL?
> >
> > Why would you be using an old kernel tree like this? That's very odd,
> > please do not do that.
> >
> > thanks,
> >
> > greg k-h
>
> Hi Greg,
>
> Thanks for the response. We have our own distro with 6.1.y kernel and we are
> trying to upgrade glibc to 2.43.
Great, then also update the kernel! Don't only do one thing.
> As 6.1.y is well within support period I
> thought it would be good to keep it working with glibc-2.43 as these are
> harmless fixes and would help many (if someone is building 6.1.y tree in
> Fedora rawhide for example).
They shouldn't be doing that :)
> Updating kernel to latest LTS is not feasible for us at the moment.
Why not? Nothing should break if you do that, just like nothing should
break when you update glibc. What prevents you from doing this, you
will then get a few thousand CVEs fixed automatically for you that are
not currently fixed in the latest 6.1.y tree.
> I will send a patch series to newer LTS releases soon. Thanks for the
> advice.
No, this should not be needed, just build the latest perf if you really
need/want it.
thanks,
greg k-h
prev parent reply other threads:[~2026-05-13 7:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 7:10 [PATCH 6.1.y v2 00/18] Backport fixes for -Wdiscarded-qualifiers and -Wnonnull with newer glibc Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 01/18] libbpf: Fix -Wdiscarded-qualifiers under C23 Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 02/18] perf diff: Constify strchr() return variables Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 03/18] perf test bpf: Address error about non-null argument for epoll_pwait 2nd arg Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 04/18] perf list: Fix -Wdiscarded-qualifiers under C23 Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 05/18] perf trace: Deal with compiler const checks Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 06/18] perf tools: Use const for variables receiving str{str,r?chr}() returns Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 07/18] perf parse-events: Fix -Wdiscarded-qualifiers under C23 Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 08/18] perf tools: Remove unused color_fwrite_lines Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 09/18] perf strlist: Don't write to const memory Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 10/18] perf metricgroup: Constify variables storing the result of strchr() on const tables Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 11/18] perf session: Don't write to memory pointed to a const pointer Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 12/18] perf trace-event: Constify variables storing the result of strchr() on const tables Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 13/18] perf units: " Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 14/18] perf bpf: Fix -Wdiscarded-qualifiers under C23 Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 15/18] perf time-utils: Constify variables storing the result of strchr() on const tables Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 16/18] perf demangle-java: " Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 17/18] perf parse-events:: Fix -Wdiscarded-qualifiers under C23 Shreenidhi Shedi
2026-05-11 7:10 ` [PATCH 6.1.y v2 18/18] perf bpf-event: Constify variables storing the result of strchr() on const tables Shreenidhi Shedi
2026-05-11 8:16 ` [PATCH 6.1.y v2 00/18] Backport fixes for -Wdiscarded-qualifiers and -Wnonnull with newer glibc Greg KH
2026-05-13 6:37 ` Shreenidhi Shedi
2026-05-13 7:21 ` Greg KH [this message]
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=2026051315-engorge-agreed-39cb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=acme@kernel.org \
--cc=linux@treblig.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=stable@vger.kernel.org \
--cc=yesshedi@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