Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) client-ip=2620:137:e000::3:5;
From:   Philipp Zabel <p.zabel@pengutronix.de>
To:     Vivek Gautam <vivek.gautam@codeaurora.org>,
        Dmitry Osipenko <digetx@gmail.com>,
        Mark Brown <broonie@kernel.org>,
        Geert Uytterhoeven <geert+renesas@glider.be>
Cc:     linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org
In-Reply-To: <2440edae7ca8534628cdbaf559ded288f2998178.1701276806.git.geert+renesas@glider.be>
References: <2440edae7ca8534628cdbaf559ded288f2998178.1701276806.git.geert+renesas@glider.be>
Subject: Re: [PATCH] reset: Fix crash when freeing non-existent optional
 resets
Message-Id: <170135319678.682649.10186168762521739609.b4-ty@pengutronix.de>
Date:   Thu, 30 Nov 2023 15:06:36 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Wed, 29 Nov 2023 17:55:33 +0100, Geert Uytterhoeven wrote:
> When obtaining one or more optional resets, non-existent resets are
> stored as NULL pointers, and all related error and cleanup paths need to
> take this into account.
> 
> Currently only reset_control_put() and reset_control_bulk_put()
> get this right.  All of __reset_control_bulk_get(),
> of_reset_control_array_get(), and reset_control_array_put() lack the
> proper checking, causing NULL pointer dereferences on failure or
> release.
> 
> [...]

Applied to reset/fixes, thanks!

[1/1] reset: Fix crash when freeing non-existent optional resets
      https://git.pengutronix.de/cgit/pza/linux/commit/?id=4a6756f56bcf

regards
Philipp