From: Conor Dooley <conor@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Z qiang <qiang.zhang1211@gmail.com>,
Conor Dooley <conor.dooley@microchip.com>,
Xiangyu Chen <xiangyu.chen@windriver.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, jslaby@suse.cz, rcu <rcu@vger.kernel.org>
Subject: Re: Linux 6.1.120
Date: Tue, 31 Dec 2024 18:41:27 +0000 [thread overview]
Message-ID: <20241231-talisman-drone-77262b2af4a9@spud> (raw)
In-Reply-To: <2024123018-lend-deflate-94d0@gregkh>
[-- Attachment #1: Type: text/plain, Size: 872 bytes --]
On Mon, Dec 30, 2024 at 03:47:26PM +0100, Greg Kroah-Hartman wrote:
> > > > > For v6.1.x kernels, the cblist_init_generic() is invoke in init task context,
> > > > > rtp->rtpcp_array is allocated use GFP_KERENL and in the critical section
> > > > > holding rcu_tasks.cbs_gbl_lock spinlock. so might_resched() trigger warnings.
> > > > > You should perform the operation of allocating rtpcp_array memory outside
> > > > > the spinlock.
> > > > > Are you willing to resend the patch?
> > > >
> > > > So should I revert this, or do you have a fixup patch somewhere?
> > >
> > > Is it too soon to push for a revert? It's interfering with my CIs
> > > attempts to test the 121-rc.
> >
> > Sure, can someone send me a revert?
>
> Nevermind, I will just do it...
That'd be great, at least from where I'm sitting, since I'm still AFK
for Christmas :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-12-31 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 20:53 Greg Kroah-Hartman
2024-12-14 20:53 ` Greg Kroah-Hartman
2024-12-16 13:24 ` Conor Dooley
2024-12-17 8:11 ` Z qiang
2024-12-17 8:28 ` Greg Kroah-Hartman
2024-12-18 16:29 ` Conor Dooley
2024-12-30 14:46 ` Greg Kroah-Hartman
2024-12-30 14:47 ` Greg Kroah-Hartman
2024-12-31 18:41 ` Conor Dooley [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=20241231-talisman-drone-77262b2af4a9@spud \
--to=conor@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=conor.dooley@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=qiang.zhang1211@gmail.com \
--cc=rcu@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xiangyu.chen@windriver.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
all inboxes | Powered by JetHome®