| 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
| ||
|
Message-ID: <a601236c-8128-ca7a-667f-12a4b7cefb89@huawei.com>
Date: Mon, 19 Aug 2019 22:26:25 +0800
From: Zenghui Yu <yuzenghui@...wei.com>
To: Marc Zyngier <maz@...nel.org>
CC: Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Julien Thierry <julien.thierry.kdev@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Lokesh Vutla <lokeshvutla@...com>,
John Garry <john.garry@...wei.com>,
<linux-kernel@...r.kernel.org>,
"Shameerali Kolothum Thodi" <shameerali.kolothum.thodi@...wei.com>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2 01/12] irqchip/gic: Rework gic_configure_irq to take
the full ICFGR base
Hi Marc,
On 2019/8/6 18:01, Marc Zyngier wrote:
> gic_configure_irq is currently passed the (re)distributor address,
> to which it applies an a fixed offset to get to the configuration
> registers. This offset is constant across all GICs, or rather it was
> until to v3.1...
>
> An easy way out is for the individual drivers to pass the base
> address of the configuration register for the considered interrupt.
> At the same time, move part of the error handling back to the
> individual drivers, as things are about to change on that front.
>
> Signed-off-by: Marc Zyngier <maz@...nel.org>
> ---
> drivers/irqchip/irq-gic-common.c | 14 +++++---------
> drivers/irqchip/irq-gic-v3.c | 11 ++++++++++-
> drivers/irqchip/irq-gic.c | 10 +++++++++-
> drivers/irqchip/irq-hip04.c | 7 ++++++-
> 4 files changed, 30 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/irqchip/irq-gic-common.c b/drivers/irqchip/irq-gic-common.c
> index b0a8215a13fc..6900b6f0921c 100644
> --- a/drivers/irqchip/irq-gic-common.c
> +++ b/drivers/irqchip/irq-gic-common.c
> @@ -63,7 +63,7 @@ int gic_configure_irq(unsigned int irq, unsigned int type,
> * for "irq", depending on "type".
> */
> raw_spin_lock_irqsave(&irq_controller_lock, flags);
> - val = oldval = readl_relaxed(base + GIC_DIST_CONFIG + confoff);
> + val = oldval = readl_relaxed(base + confoff);
> if (type & IRQ_TYPE_LEVEL_MASK)
> val &= ~confmask;
> else if (type & IRQ_TYPE_EDGE_BOTH)
> @@ -83,14 +83,10 @@ int gic_configure_irq(unsigned int irq, unsigned int type,
> * does not allow us to set the configuration or we are in a
> * non-secure mode, and hence it may not be catastrophic.
> */
> - writel_relaxed(val, base + GIC_DIST_CONFIG + confoff);
> - if (readl_relaxed(base + GIC_DIST_CONFIG + confoff) != val) {
> - if (WARN_ON(irq >= 32))
> - ret = -EINVAL;
Since this WARN_ON is dropped, the comment above should also be updated.
But what is the reason for deleting it? (It may give us some points
when we fail to set type for SPIs.)
Thanks,
zenghui
> - else
> - pr_warn("GIC: PPI%d is secure or misconfigured\n",
> - irq - 16);
> - }
> + writel_relaxed(val, base + confoff);
> + if (readl_relaxed(base + confoff) != val)
> + ret = -EINVAL;
> +
> raw_spin_unlock_irqrestore(&irq_controller_lock, flags);
>
> if (sync_access)
> diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
> index 96d927f0f91a..b250e69908f8 100644
> --- a/drivers/irqchip/irq-gic-v3.c
> +++ b/drivers/irqchip/irq-gic-v3.c
> @@ -407,6 +407,7 @@ static int gic_set_type(struct irq_data *d, unsigned int type)
> unsigned int irq = gic_irq(d);
> void (*rwp_wait)(void);
> void __iomem *base;
> + int ret;
>
> /* Interrupt configuration for SGIs can't be changed */
> if (irq < 16)
> @@ -425,7 +426,15 @@ static int gic_set_type(struct irq_data *d, unsigned int type)
> rwp_wait = gic_dist_wait_for_rwp;
> }
>
> - return gic_configure_irq(irq, type, base, rwp_wait);
> +
> + ret = gic_configure_irq(irq, type, base + GICD_ICFGR, rwp_wait);
> + if (ret && irq < 32) {
> + /* Misconfigured PPIs are usually not fatal */
> + pr_warn("GIC: PPI%d is secure or misconfigured\n", irq - 16);
> + ret = 0;
> + }
> +
> + return ret;
> }
>
> static int gic_irq_set_vcpu_affinity(struct irq_data *d, void *vcpu)
> diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
> index e45f45e68720..ab48760acabb 100644
> --- a/drivers/irqchip/irq-gic.c
> +++ b/drivers/irqchip/irq-gic.c
> @@ -291,6 +291,7 @@ static int gic_set_type(struct irq_data *d, unsigned int type)
> {
> void __iomem *base = gic_dist_base(d);
> unsigned int gicirq = gic_irq(d);
> + int ret;
>
> /* Interrupt configuration for SGIs can't be changed */
> if (gicirq < 16)
> @@ -301,7 +302,14 @@ static int gic_set_type(struct irq_data *d, unsigned int type)
> type != IRQ_TYPE_EDGE_RISING)
> return -EINVAL;
>
> - return gic_configure_irq(gicirq, type, base, NULL);
> + ret = gic_configure_irq(gicirq, type, base + GIC_DIST_CONFIG, NULL);
> + if (ret && gicirq < 32) {
> + /* Misconfigured PPIs are usually not fatal */
> + pr_warn("GIC: PPI%d is secure or misconfigured\n", gicirq - 16);
> + ret = 0;
> + }
> +
> + return ret;
> }
>
> static int gic_irq_set_vcpu_affinity(struct irq_data *d, void *vcpu)
> diff --git a/drivers/irqchip/irq-hip04.c b/drivers/irqchip/irq-hip04.c
> index cf705827599c..1626131834a6 100644
> --- a/drivers/irqchip/irq-hip04.c
> +++ b/drivers/irqchip/irq-hip04.c
> @@ -130,7 +130,12 @@ static int hip04_irq_set_type(struct irq_data *d, unsigned int type)
>
> raw_spin_lock(&irq_controller_lock);
>
> - ret = gic_configure_irq(irq, type, base, NULL);
> + ret = gic_configure_irq(irq, type, base + GIC_DIST_CONFIG, NULL);
> + if (ret && irq < 32) {
> + /* Misconfigured PPIs are usually not fatal */
> + pr_warn("GIC: PPI%d is secure or misconfigured\n", irq - 16);
> + ret = 0;
> + }
>
> raw_spin_unlock(&irq_controller_lock);
>
>
Powered by blists - more mailing lists