From: Yingjoe Chen <yingjoe.chen@mediatek.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Beniamino Galvani <b.galvani@gmail.com>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
<srv_heupstream@mediatek.com>, <hc.yen@mediatek.com>,
<yh.chen@mediatek.com>, <linux-kernel@vger.kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
<nathan.chung@mediatek.com>, Sascha Hauer <kernel@pengutronix.de>,
<eddie.huang@mediatek.com>, <yingjoe.chen@gmail.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] irqchip: mediatek: Fix error return code detection
Date: Tue, 9 Dec 2014 14:11:29 +0800 [thread overview]
Message-ID: <1418105489.32622.11.camel@mtksdaap41> (raw)
In-Reply-To: <alpine.DEB.2.11.1412082114340.16275@nanos>
On Mon, 2014-12-08 at 21:30 +0100, Thomas Gleixner wrote:
> On Mon, 8 Dec 2014, Yingjoe Chen wrote:
>
> > This fix an error handling bug reported by Beniamino, this is based on
> > mtk intpol patches [1]
> >
> > Joe.C
> >
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2014-November/305808.html
> >
> > ====================
> > of_io_request_and_map() return ERR_PTR wrapped error code instead of
> > NULL when fail, fix code in mtk_sysirq_of_init() to correctly handle
> > this.
> >
> > Signed-off-by: Yingjoe Chen <yingjoe.chen@mediatek.com>
>
> This is not a proper changelog. Let me write up a proper one:
>
> Subject: irqchip: mediatek: Use IS_ERR() instead of NULL pointer check
>
> Beniamino reported a kernel oops caused by an invalid DT file for the
> mediatek interrupt polarity extension.
>
> The reason is that the interrupt polarity support for mediatek chips
> merily checks for at NULL pointer instead of a casted error return
> value in mtk_sysirq_of_init() so any other casted error value passes
> the NULL pointer check and causes a kernel panic when dereferenced.
>
> Use IS_ERR() and return the error value via PTR_ERR().
>
> Reported-and-tested-by: Beniamino Galvani <b.galvani@gmail.com>
> Signed-off-by: Yingjoe Chen <yingjoe.chen@mediatek.com>
>
> Can you see the difference?
>
> Thanks,
>
> tglx
Thanks for the review.
This changelog describe issue and why we need this change more clearly.
I'll prepare a new patch with this changelog, Thanks.
Joe.C
next prev parent reply other threads:[~2014-12-09 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 15:03 [PATCH] irqchip: mediatek: Fix error return code detection Yingjoe Chen
2014-12-08 20:30 ` Thomas Gleixner
2014-12-09 6:11 ` Yingjoe Chen [this message]
2014-12-10 9:55 ` [PATCH v2] irqchip: mediatek: Use IS_ERR() instead of NULL pointer check Yingjoe Chen
2014-12-10 12:14 ` Beniamino Galvani
2014-12-10 12:53 ` Jason Cooper
2014-12-10 13:55 ` Yingjoe Chen
2014-12-10 20:08 ` Beniamino Galvani
2014-12-12 15:15 ` [PATCH v3] irqchip: mtk-sysirq: " Yingjoe Chen
2015-01-07 2:08 ` [PATCH v2] irqchip: mediatek: " Jason Cooper
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=1418105489.32622.11.camel@mtksdaap41 \
--to=yingjoe.chen@mediatek.com \
--cc=b.galvani@gmail.com \
--cc=eddie.huang@mediatek.com \
--cc=hc.yen@mediatek.com \
--cc=jason@lakedaemon.net \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=nathan.chung@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=tglx@linutronix.de \
--cc=yh.chen@mediatek.com \
--cc=yingjoe.chen@gmail.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