From: "Erhard F." <erhard_f@mailbox.org>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: kernel test robot <oliver.sang@intel.com>,
Luis Chamberlain <mcgrof@kernel.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Zhen Lei <thunder.leizhen@huawei.com>
Subject: Re: [PATCH] kallsyms: Fix scheduling with interrupts disabled in self-test
Date: Thu, 12 Jan 2023 18:30:19 +0100 [thread overview]
Message-ID: <20230112183019.29171b26@yea> (raw)
In-Reply-To: <20230112105426.1037325-1-npiggin@gmail.com>
On Thu, 12 Jan 2023 20:54:26 +1000
Nicholas Piggin <npiggin@gmail.com> wrote:
> kallsyms_on_each* may schedule so must not be called with interrupts
> disabled. The iteration function could disable interrupts, but this
> also changes lookup_symbol() to match the change to the other timing
> code.
Just tested your patch. It fixes the problem on the G5. Thanks!
Regards,
Erhard
next prev parent reply other threads:[~2023-01-12 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 10:54 [PATCH] kallsyms: Fix scheduling with interrupts disabled in self-test Nicholas Piggin
2023-01-12 17:30 ` Erhard F. [this message]
2023-01-12 18:24 ` Luis Chamberlain
2023-01-13 8:44 ` Petr Mladek
2023-01-13 23:13 ` Luis Chamberlain
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=20230112183019.29171b26@yea \
--to=erhard_f@mailbox.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mcgrof@kernel.org \
--cc=npiggin@gmail.com \
--cc=oliver.sang@intel.com \
--cc=thunder.leizhen@huawei.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;
as well as URLs for NNTP newsgroup(s).