From: Marc Zyngier <marc.zyngier@arm.com>
To: "Zhao, Yuanyuan" <yuanyuan.zhao@hxt-semitech.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"jason@lakedaemon.net" <jason@lakedaemon.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Zheng, Joey" <yu.zheng@hxt-semitech.com>,
"Wang, Dongsheng" <dongsheng.wang@hxt-semitech.com>
Subject: Re: [RESEND 1/1] gic: its: Make sure a LPI is discarded before free.
Date: Wed, 9 Jan 2019 09:52:08 +0000 [thread overview]
Message-ID: <38d7afaf-e800-f6e7-83e3-eb006f4d6f4c@arm.com> (raw)
In-Reply-To: <c81f42aa93904353bbeac590da7b0945@HXTBJIDCEMVIW02.hxtcorp.net>
On 09/01/2019 09:29, Zhao, Yuanyuan wrote:
> Hi Marc:
>
> Thank you for your reply.
>
> As you said, APIs such as free_irq will deactivate irq
> before free it. But deactivation is not forced by every API,
> for example irq_dispose_mapping. So I think it's better to check
> that irq was deactivated as expected.
In general, we should fix the problem at the core API level instead of
hacking individual drivers.
But more to the point, irq_dispose_mapping is not supposed to do
anything with the an active irq, as it doesn't have the required
information to safely remove it.
So calling irq_dispose_mapping on an interrupt that still has registered
actions is a bug, and I'm not convinced we want to cater for such a
case. Do you have a concrete example of some kernel code expecting this
behaviour?
Thanks,
M.
>
> BRs,
> Yuanyuan
>
>
>> -----Original Message-----
>> From: Marc Zyngier [mailto:marc.zyngier@arm.com]
>> Sent: 2019年1月9日 15:43
>> To: Zhao, Yuanyuan <yuanyuan.zhao@hxt-semitech.com>
>> Cc: tglx@linutronix.de; jason@lakedaemon.net; linux-
>> kernel@vger.kernel.org; linux-arm-kernel@lists.infradead.org; Zheng, Joey
>> <yu.zheng@hxt-semitech.com>; Wang, Dongsheng <dongsheng.wang@hxt-
>> semitech.com>
>> Subject: Re: [RESEND 1/1] gic: its: Make sure a LPI is discarded before free.
>>
>> On Wed, 9 Jan 2019 11:53:27 +0800
>> Zhao Yuanyuan <yuanyuan.zhao@hxt-semitech.com> wrote:
>>
>> Hi Zhao,
>>
>>> Its device will be removed after all events be freed.
>>> Undisarded events can lead to unpredictable behaviar.
>>>
>>> Signed-off-by: Zhao Yuanyuan <yuanyuan.zhao@hxt-semitech.com>
>>> ---
>>> drivers/irqchip/irq-gic-v3-its.c | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/drivers/irqchip/irq-gic-v3-its.c
>>> b/drivers/irqchip/irq-gic-v3-its.c
>>> index db20e99..4fee008 100644
>>> --- a/drivers/irqchip/irq-gic-v3-its.c
>>> +++ b/drivers/irqchip/irq-gic-v3-its.c
>>> @@ -2572,6 +2572,10 @@ static void its_irq_domain_free(struct
>> irq_domain *domain, unsigned int virq,
>>> virq + i);
>>> u32 event = its_get_event_id(data);
>>>
>>> + /* Discard irq before free */
>>> + if (irqd_is_activated(d))
>>> + its_send_discard(its_dev, event);
>>> +
>>> /* Mark interrupt index as unused */
>>> clear_bit(event, its_dev->event_map.lpi_map);
>>>
>>
>> But we already do send a discard on deactivate, which logically happens
>> before we free the domain. So what are you fixing here?
>>
>> Thanks,
>>
>> M.
>> --
>> Without deviation from the norm, progress is not possible.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2019-01-09 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 8:20 [PATCH " Zhao Yuanyuan
2019-01-09 3:53 ` [RESEND " Zhao Yuanyuan
2019-01-09 7:43 ` Marc Zyngier
2019-01-09 9:29 ` Zhao, Yuanyuan
2019-01-09 9:52 ` Marc Zyngier [this message]
2019-01-10 9:42 ` Zhao, Yuanyuan
2019-01-10 12:55 ` Marc Zyngier
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=38d7afaf-e800-f6e7-83e3-eb006f4d6f4c@arm.com \
--to=marc.zyngier@arm.com \
--cc=dongsheng.wang@hxt-semitech.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yu.zheng@hxt-semitech.com \
--cc=yuanyuan.zhao@hxt-semitech.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
all inboxes | Powered by JetHome®