From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753635AbdK0U6N (ORCPT ); Mon, 27 Nov 2017 15:58:13 -0500 Received: from mail.kernel.org ([198.145.29.99]:40218 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753587AbdK0U6K (ORCPT ); Mon, 27 Nov 2017 15:58:10 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9BCB721909 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=atull@kernel.org From: Alan Tull To: Rob Herring , Frank Rowand , Pantelis Antoniou Cc: Moritz Fischer , Alan Tull , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org Subject: [RFC 0/2] of: Add whitelist Date: Mon, 27 Nov 2017 14:58:02 -0600 Message-Id: <1511816284-12145-1-git-send-email-atull@kernel.org> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Here's a proposal for a whitelist to lock down the dynamic device tree. For an overlay to be accepted, all of its targets are required to be on a target node whitelist. Currently the only way I have to get on the whitelist is calling a function to add a node. That works for fpga regions, but I think other uses will need a way of having adding specific nodes from the base device tree, such as by adding a property like 'allow-overlay;' or 'allow-overlay = "okay";' If that is acceptable, I could use some advice on where that particular code should go. Alan Alan Tull (2): of: overlay: add whitelist fpga: of region: add of-fpga-region to whitelist drivers/fpga/of-fpga-region.c | 9 ++++++ drivers/of/overlay.c | 73 +++++++++++++++++++++++++++++++++++++++++++ include/linux/of.h | 12 +++++++ 3 files changed, 94 insertions(+) -- 2.7.4