From: "Benno Lossin" <lossin@kernel.org>
To: "Gary Guo" <gary@garyguo.net>,
"Greg KH" <gregkh@linuxfoundation.org>,
"Miguel Ojeda" <ojeda@kernel.org>
Cc: <achill@achill.org>, <akpm@linux-foundation.org>,
<broonie@kernel.org>, <conor@kernel.org>, <f.fainelli@gmail.com>,
<hargar@microsoft.com>, <jonathanh@nvidia.com>,
<linux-kernel@vger.kernel.org>, <linux@roeck-us.net>,
<lkft-triage@lists.linaro.org>, <patches@kernelci.org>,
<patches@lists.linux.dev>, <pavel@nabladev.com>, <rwarsow@gmx.de>,
<shuah@kernel.org>, <sr@sladewatkins.com>,
<stable@vger.kernel.org>, <sudipm.mukherjee@gmail.com>,
<torvalds@linux-foundation.org>
Subject: Re: [PATCH 6.6 000/175] 6.6.131-rc1 review
Date: Thu, 02 Apr 2026 14:07:09 +0200 [thread overview]
Message-ID: <DHINN8SUUZSW.2LM7XEUJ2M2B0@kernel.org> (raw)
In-Reply-To: <DHINJ6CUHNLM.3RD5BA5313NKK@garyguo.net>
On Thu Apr 2, 2026 at 2:01 PM CEST, Gary Guo wrote:
> On Thu Apr 2, 2026 at 12:52 PM BST, Greg KH wrote:
>> On Thu, Apr 02, 2026 at 01:27:12PM +0200, Miguel Ojeda wrote:
>>> On Tue, 31 Mar 2026 18:19:44 +0200 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>>> >
>>> > This is the start of the stable review cycle for the 6.6.131 release.
>>> > There are 175 patches in this series, all will be posted as a response
>>> > to this one. If anyone has any issues with these being applied, please
>>> > let me know.
>>> >
>>> > Responses should be made by Thu, 02 Apr 2026 16:16:56 +0000.
>>> > Anything received after that time might be too late.
>>>
>>> The pin-init change does not build:
>>>
>>> error[E0425]: cannot find value `__refcount_guard` in this scope
>>> --> rust/kernel/init/macros.rs:1320:25
>>> |
>>> 1320 | @guards([< __ $field _guard >], $($guards,)*),
>>> | ^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
>>> |
>>> ::: rust/kernel/sync/arc.rs:529:49
>>> |
>>> 529 | let inner = Box::try_init::<AllocError>(try_init!(ArcInner {
>>> | _________________________________________________-
>>> 530 | | // SAFETY: There are no safety requirements for this FFI call.
>>> 531 | | refcount: Opaque::new(unsafe { bindings::REFCOUNT_INIT(1) }),
>>> 532 | | data <- init::uninit::<T, AllocError>(),
>>> 533 | | }? AllocError))?;
>>> | |______________________- in this macro invocation
>>> |
>>> = note: this error originates in the macro `$crate::__init_internal` which comes from the expansion of the macro `try_init` (in Nightly builds, run with -Z macro-backtrace for more info)
>>>
>>> (among other errors)
>>>
>>> I would suggest dropping these for now:
>>>
>>> 0565326613fa ("rust: pin-init: internal: init: document load-bearing fact of field accessors")
>>> 66655aacfa42 ("rust: pin-init: add references to previously initialized fields")
>>>
>>> Cc: Benno Lossin <lossin@kernel.org>
>>> Cc: Gary Guo <gary@garyguo.net>
>>
>> Crap, I just did a realease. Let me go revert these and do a new
>> release with that fixed, sorry about that, I guess my builds weren't
>> testing rust on older kernels, my fault :(
I don't know what happened with this series :( Sorry for the extra work.
> It is probably missing a dependency patch. I could take a look next week, but
> perhaps not backporting to 6.6 is an easier solution :)
Yeah let's do that.
Cheers,
Benno
prev parent reply other threads:[~2026-04-02 12:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 16:19 [PATCH 6.6 000/175] 6.6.131-rc1 review Greg Kroah-Hartman
2026-03-31 21:48 ` Florian Fainelli
2026-04-01 1:32 ` Peter Schneider
2026-04-01 6:46 ` Shung-Hsi Yu
2026-04-01 7:28 ` Brett A C Sheffield
2026-04-01 9:19 ` Jon Hunter
2026-04-01 9:34 ` Ron Economos
2026-04-01 10:26 ` Barry K. Nathan
2026-04-01 11:39 ` Francesco Dolcini
2026-04-01 16:22 ` Shuah Khan
2026-04-02 11:27 ` Miguel Ojeda
2026-04-02 11:52 ` Greg KH
2026-04-02 12:01 ` Gary Guo
2026-04-02 12:07 ` Benno Lossin [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=DHINN8SUUZSW.2LM7XEUJ2M2B0@kernel.org \
--to=lossin@kernel.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--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=ojeda@kernel.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--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