From: Thomas Gleixner <tglx@linutronix.de>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
David Daney <david.daney@cavium.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] irqdomain: check for NULL before dereferencing
Date: Fri, 25 Aug 2017 10:45:15 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1708251042500.1883@nanos> (raw)
In-Reply-To: <20170825071337.g72afdd5pdqjshon@mwanda>
On Fri, 25 Aug 2017, Dan Carpenter wrote:
> I reversed these two checks so we check "root_irq_data" for NULL before
> dereferencing it.
Can you please start to write coherent changelogs? See
Documentation/process/submitting-patches.rst
The above describes the change you made which is completely pointless
because we can see the change in the patch.
What's missing is WHY this is required and WHAT the problem with the
existing code is.
Thanks,
tglx
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
> index b9c688944429..e84b7056bb08 100644
> --- a/kernel/irq/irqdomain.c
> +++ b/kernel/irq/irqdomain.c
> @@ -1505,10 +1505,10 @@ int irq_domain_push_irq(struct irq_domain *domain, int virq, void *arg)
> if (WARN_ON(!irq_domain_is_hierarchy(domain)))
> return -EINVAL;
>
> - if (domain->parent != root_irq_data->domain)
> + if (!root_irq_data)
> return -EINVAL;
>
> - if (!root_irq_data)
> + if (domain->parent != root_irq_data->domain)
> return -EINVAL;
>
> child_irq_data = kzalloc_node(sizeof(*child_irq_data), GFP_KERNEL,
>
next prev parent reply other threads:[~2017-08-25 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 7:13 Dan Carpenter
2017-08-25 8:45 ` Thomas Gleixner [this message]
2017-08-25 9:10 ` [PATCH v2] irqdomain: potential Oops in irq_domain_push_irq() Dan Carpenter
2017-08-25 11:08 ` Thomas Gleixner
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=alpine.DEB.2.20.1708251042500.1883@nanos \
--to=tglx@linutronix.de \
--cc=dan.carpenter@oracle.com \
--cc=david.daney@cavium.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.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®