From: Greg KH <gregkh@linuxfoundation.org>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [REGRESSION] [BISECTED] linux-6.6.y and linux-6.12.y: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al
Date: Sun, 17 Aug 2025 16:05:20 +0200 [thread overview]
Message-ID: <2025081751-accurate-eradicate-9456@gregkh> (raw)
In-Reply-To: <20250817134329.GC2771@pc21.mareichelt.com>
On Sun, Aug 17, 2025 at 03:43:29PM +0200, Markus Reichelt wrote:
> * Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > > I have bisected the issue to the commits
> > > 33c778ea0bd0fa62ff590497e72562ff90f82b13 in 6.6.102 and
> > > fc1072d934f687e1221d685cf1a49a5068318f34 in 6.12.42 which are both the
> > > same change code-wise (upstream commit
> > > ff7ec8dc1b646296f8d94c39339e8d3833d16c05).
> > >
> > > Reverting these commits makes xosview and gkrellm "work" again as in
> > > they both show network traffic again.
> >
> > Is this also an issue in 6.16.1 and 6.17-rc1?
>
> I can confirm the issue with gkrellm on 6.16.1 (and 6.15.10 fwiw).
>
Great, we are bug compatible!
Please work with the developers of those changes to resolve the
regression in Linus's tree and then we can backport the needed fixes.
thanks,
greg k-h
next prev parent reply other threads:[~2025-08-17 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 17:56 [REGRESSION] [BISECTED] linux-6.6.y and linux-6.12.y: proc: use the same treatment to check proc_lseek as ones for proc_read_iter et.al Lars Wendler
2025-08-16 5:39 ` Greg KH
2025-08-17 13:43 ` Markus Reichelt
2025-08-17 14:05 ` Greg KH [this message]
2025-08-18 1:15 ` wangzijie
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=2025081751-accurate-eradicate-9456@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.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.