From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Traceback with CONFIG_REGMAP_KUNIT=y+CONFIG_DEBUG_ATOMIC_SLEEP=y
Date: Thu, 20 Jul 2023 10:22:43 -0700 [thread overview]
Message-ID: <c77080a5-255d-9584-4031-2dd27dc8fa51@roeck-us.net> (raw)
In-Reply-To: <0e64a83a-fb53-48c4-b790-8e8dfa888ef3@sirena.org.uk>
On 7/20/23 09:48, Mark Brown wrote:
> On Thu, Jul 20, 2023 at 09:41:42AM -0700, Guenter Roeck wrote:
>
>> After adding the GFP_KERNEL -> map->alloc_flags changes to the maple tree
>> code while skipping the init functions, I no longer see the traceback.
>> This is without my patches.
>
> Ah, excellent - yes, that should sort it. I've already queued your
> original patch for CI for 6.5, we could then apply both your new patch
> and Dan's for 6.6 to support anyone who for some reason does want to try
> dynamic allocation at runtime in atomic context.
Makes sense. I submitted a patch to address the problem in the maple tree
code. I assume Dan will submit one for the rbtree code. Dan, let me know
if you want me to handle that one as well.
Thanks,
Guenter
prev parent reply other threads:[~2023-07-20 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 22:37 Guenter Roeck
2023-07-19 23:05 ` Mark Brown
2023-07-20 8:50 ` Dan Carpenter
2023-07-20 14:26 ` Guenter Roeck
2023-07-20 14:31 ` Mark Brown
2023-07-20 15:03 ` Guenter Roeck
2023-07-20 15:07 ` Mark Brown
2023-07-20 16:25 ` Guenter Roeck
2023-07-20 16:36 ` Mark Brown
2023-07-20 16:41 ` Guenter Roeck
2023-07-20 16:48 ` Mark Brown
2023-07-20 17:22 ` Guenter Roeck [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=c77080a5-255d-9584-4031-2dd27dc8fa51@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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 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®