From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Cc: peterz@infradead.org, pmenzel@molgen.mpg.de
Subject: Re: [PATCH] powerpc/code-patching: Pre-map patch area
Date: Tue, 08 Mar 2022 23:07:46 +1100 [thread overview]
Message-ID: <164674126664.3322453.2623564151161334844.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <20220223015821.473097-1-mpe@ellerman.id.au>
On Wed, 23 Feb 2022 12:58:21 +1100, Michael Ellerman wrote:
> Paul reported a warning with DEBUG_ATOMIC_SLEEP=y:
>
> BUG: sleeping function called from invalid context at include/linux/sched/mm.h:256
> in_atomic(): 0, irqs_disabled(): 1, non_block: 0, pid: 1, name: swapper/0
> preempt_count: 0, expected: 0
> ...
> Call Trace:
> dump_stack_lvl+0xa0/0xec (unreliable)
> __might_resched+0x2f4/0x310
> kmem_cache_alloc+0x220/0x4b0
> __pud_alloc+0x74/0x1d0
> hash__map_kernel_page+0x2cc/0x390
> do_patch_instruction+0x134/0x4a0
> arch_jump_label_transform+0x64/0x78
> __jump_label_update+0x148/0x180
> static_key_enable_cpuslocked+0xd0/0x120
> static_key_enable+0x30/0x50
> check_kvm_guest+0x60/0x88
> pSeries_smp_probe+0x54/0xb0
> smp_prepare_cpus+0x3e0/0x430
> kernel_init_freeable+0x20c/0x43c
> kernel_init+0x30/0x1a0
> ret_from_kernel_thread+0x5c/0x64
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/code-patching: Pre-map patch area
https://git.kernel.org/powerpc/c/591b4b268435f00d2f0b81f786c2c7bd5ef66416
cheers
prev parent reply other threads:[~2022-03-08 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 1:58 [PATCH] powerpc/code-patching: Pre-map patch area Michael Ellerman
2022-03-08 12:07 ` Michael Ellerman [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=164674126664.3322453.2623564151161334844.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=peterz@infradead.org \
--cc=pmenzel@molgen.mpg.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.