From: Greg KH <greg@kroah.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: stable@vger.kernel.org,
Navid Emamdoost <navid.emamdoost@gmail.com>,
Alexandru Ardelean <alexandru.ardelean@analog.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v2 stable v4.4+ 1/2] iio: imu: adis16400: release allocated memory on failure
Date: Mon, 15 Mar 2021 13:12:00 +0100 [thread overview]
Message-ID: <YE9PEKdZWznxnMUo@kroah.com> (raw)
In-Reply-To: <20210313172950.6224-1-krzysztof.kozlowski@canonical.com>
On Sat, Mar 13, 2021 at 06:29:49PM +0100, Krzysztof Kozlowski wrote:
> From: Navid Emamdoost <navid.emamdoost@gmail.com>
>
> commit ab612b1daf415b62c58e130cb3d0f30b255a14d0 upstream.
>
> In adis_update_scan_mode, if allocation for adis->buffer fails,
> previously allocated adis->xfer needs to be released.
>
> Signed-off-by: Navid Emamdoost <navid.emamdoost@gmail.com>
> Reviewed-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
>
> ---
>
> Changes since v1:
> 1. Add also this one for backport: v4.4 - v4.14. Newer should take
> direct cherry pick
> ---
> drivers/iio/imu/adis_buffer.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
Both patches now queued up, thanks for the backports.
greg k-h
prev parent reply other threads:[~2021-03-15 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 17:29 [PATCH v2 stable v4.4+ 1/2] iio: imu: adis16400: release allocated memory on failure Krzysztof Kozlowski
2021-03-13 17:29 ` [PATCH v2 stable v4.4+ 2/2] iio: imu: adis16400: fix memory leak Krzysztof Kozlowski
2021-03-15 12:12 ` Greg KH [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=YE9PEKdZWznxnMUo@kroah.com \
--to=greg@kroah.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alexandru.ardelean@analog.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=navid.emamdoost@gmail.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.