From: Kevin Hilman <khilman@baylibre•com>
To: Remi Pommarel <repk@triplefau•lt>,
Jonathan Cameron <jic23@kernel•org>,
Hartmut Knaack <knaack.h@gmx•de>,
Lars-Peter Clausen <lars@metafoo•de>,
Peter Meerwald-Stadler <pmeerw@pmeerw•net>
Cc: Neil Armstrong <narmstrong@baylibre•com>,
Martin Blumenstingl <martin.blumenstingl@googlemail•com>,
Elie Roudninski <xademax@gmail•com>,
linux-kernel@vger•kernel.org, linux-iio@vger•kernel.org,
Remi Pommarel <repk@triplefau•lt>,
linux-amlogic@lists•infradead.org,
linux-arm-kernel@lists•infradead.org
Subject: Re: [PATCH] iio: adc: meson_saradc: Fix memory allocation order
Date: Wed, 04 Sep 2019 17:02:30 -0700 [thread overview]
Message-ID: <7h8sr3txt5.fsf@baylibre.com> (raw)
In-Reply-To: <20190901105410.23567-1-repk@triplefau.lt>
Remi Pommarel <repk@triplefau•lt> writes:
> meson_saradc's irq handler uses priv->regmap so make sure that it is
> allocated before the irq get enabled.
>
> This also fixes crash when CONFIG_DEBUG_SHIRQ is enabled, as device
> managed resources are freed in the inverted order they had been
> allocated, priv->regmap was freed before the spurious fake irq that
> CONFIG_DEBUG_SHIRQ adds called the handler.
>
> Reported-by: Elie Roudninski <xademax@gmail•com>
> Signed-off-by: Remi Pommarel <repk@triplefau•lt>
Reviewed-by: Kevin Hilman <khilman@baylibre•com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-09-05 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-01 10:54 [PATCH] iio: adc: meson_saradc: Fix memory allocation order Remi Pommarel
2019-09-01 11:29 ` Martin Blumenstingl
2019-09-02 20:40 ` Elie Roudninski
2019-09-08 11:33 ` Jonathan Cameron
2019-09-05 0:02 ` Kevin Hilman [this message]
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=7h8sr3txt5.fsf@baylibre.com \
--to=khilman@baylibre$(echo .)com \
--cc=jic23@kernel$(echo .)org \
--cc=knaack.h@gmx$(echo .)de \
--cc=lars@metafoo$(echo .)de \
--cc=linux-amlogic@lists$(echo .)infradead.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-iio@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=martin.blumenstingl@googlemail$(echo .)com \
--cc=narmstrong@baylibre$(echo .)com \
--cc=pmeerw@pmeerw$(echo .)net \
--cc=repk@triplefau$(echo .)lt \
--cc=xademax@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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