mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Peter Schneider <pschneider1968@googlemail.com>
Cc: Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@nabladev.com, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
	hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
	sr@sladewatkins.com
Subject: Re: [PATCH 6.6 0000/1674] 6.6.160-rc1 review
Date: Tue, 20 Oct 2026 09:43:27 +0200	[thread overview]
Message-ID: <2026102018-staunch-evidence-bc19@gregkh> (raw)
In-Reply-To: <892078c7-7fa1-4e32-a00f-1ac907c0ebcc@googlemail.com>

On Mon, Oct 19, 2026 at 09:10:50PM +0200, Peter Schneider wrote:
> Am 19.10.2026 um 18:54 schrieb Sasha Levin:
> > On Mon, Oct 19, 2026 at 06:02:37AM +0200, Peter Schneider wrote:
> > > # first bad commit: [7c1e132b0967210526de05e7af6f1c26ad0c1516] sysfs: Introduce a mechanism to hide static attribute_groups
> > 
> > Thanks for bisecting this.
> > 
> > > I think the problem is, that if you take this patch for stable, you need to also take the patch which is upstream [
> > > cd69fedf58f8ab1ab511f7c6ac1969cebf1c935f] sysfs: Fix crash on empty group attributes array. It addresses the exact crash
> > > that I've run into.
> > 
> > Rather than adding cd69fedf58f8, I dropped d87c295f599c ("sysfs: Introduce a
> > mechanism to hide static attribute_groups") and its dependent c7fbb8218b4a
> > ("sysfs: check visibility before changing group attribute ownership") from the
> > 6.6 and 6.1 queues.
> > 
> 
> Yeah, that seems to be the cleaner approach. I just tested this, and this works fine, too.
> 
> Will there be an -rc2?

Based on all of the reports, yes.

  reply	other threads:[~2026-10-20  7:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17 15:37 Greg Kroah-Hartman
2026-10-17 19:03 ` Brett A C Sheffield
2026-10-18  5:54 ` Peter Schneider
2026-10-19  4:02   ` Peter Schneider
2026-10-19 16:54     ` Sasha Levin
2026-10-19 19:10       ` Peter Schneider
2026-10-20  7:43         ` Greg Kroah-Hartman [this message]
2026-10-18  6:05 ` Wentao Guan
2026-10-18  9:48 ` Miguel Ojeda
2026-10-19  0:14   ` Sasha Levin
2026-10-19  6:46 ` Ron Economos
2026-10-19 10:18 ` Jon Hunter
2026-10-19 16:54   ` Sasha Levin
2026-10-19 16:55   ` Pavel Machek
2026-10-19 17:32 ` Florian Fainelli
2026-10-19 23:52 ` Shuah Khan

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=2026102018-staunch-evidence-bc19@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@nabladev.com \
    --cc=pschneider1968@googlemail.com \
    --cc=rwarsow@gmx.de \
    --cc=sashal@kernel.org \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®