From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
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 17:48:30 +0100 [thread overview]
Message-ID: <0e64a83a-fb53-48c4-b790-8e8dfa888ef3@sirena.org.uk> (raw)
In-Reply-To: <9595effb-e01c-6c5c-362e-b8e8ad364fd7@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-07-20 16:48 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 [this message]
2023-07-20 17:22 ` Guenter Roeck
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=0e64a83a-fb53-48c4-b790-8e8dfa888ef3@sirena.org.uk \
--to=broonie@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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®