linux-kernel - Re: [PATCH] PCI: keystone: fix crash with deferred probe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20151123113902.GM8644@n2100.arm.linux.org.uk>
Date:	Mon, 23 Nov 2015 11:39:02 +0000
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Jisheng Zhang <jszhang@...vell.com>
Cc:	Sekhar Nori <nsekhar@...com>, Bjorn Helgaas <bhelgaas@...gle.com>,
	linux-pci@...r.kernel.org, Murali Karicheri <m-karicheri2@...com>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] PCI: keystone: fix crash with deferred probe

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/