From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI: keystone: fix crash with deferred probe
Date: Mon, 23 Nov 2015 11:39:02 +0000 [thread overview]
Message-ID: <20151123113902.GM8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20151123192209.38e2c101@xhacker>
On Mon, Nov 23, 2015 at 07:22:09PM +0800, Jisheng Zhang wrote:
> when trying to add berlin pcie support and came up one patch
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-November/384575.html
>
> when build testing, I also realized this issue, but keystone relies on
> hook_fault_code() which is will be freed after boot, so your patch isn't
> completed.
hook_fault_code() is intentionally not callable after boot. It's unsafe
to try to change the fault handling for a running system. It's even more
unsafe to try to remove a fault handler which is located in module code.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2015-11-23 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 11:17 [PATCH] PCI: keystone: fix crash with deferred probe Sekhar Nori
2015-11-23 11:22 ` Jisheng Zhang
2015-11-23 11:27 ` Jisheng Zhang
2015-11-23 16:48 ` Sekhar Nori
2015-11-23 11:39 ` Russell King - ARM Linux [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=20151123113902.GM8644@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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