All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lars Wendler <polynomial-c@gmx.de>
Cc: wangzijie <wangzijie1@honor.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Linux kernel regressions list <regressions@lists.linux.dev>
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: Sat, 16 Aug 2025 07:39:42 +0200	[thread overview]
Message-ID: <2025081615-anew-willpower-adca@gregkh> (raw)
In-Reply-To: <20250815195616.64497967@chagall.paradoxon.rec>

On Fri, Aug 15, 2025 at 07:56:16PM +0200, Lars Wendler wrote:
> Hi,
> 
> the stable LTS linux kernels 6.6.102 and 6.12.42 have a regression
> regarding network interface monitoring with xosview and gkrellm. Both
> programs no longer show any network traffic with gkrellm even
> considering all network interfaces as being in down state. I haven't
> checked other LTS kernels so I cannot tell if there are more affected
> kernel branches.
> 
> 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?

thanks,

greg k-h

  reply	other threads:[~2025-08-16  5:39 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 [this message]
2025-08-17 13:43   ` Markus Reichelt
2025-08-17 14:05     ` Greg KH
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=2025081615-anew-willpower-adca@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=polynomial-c@gmx.de \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=wangzijie1@honor.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 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.