From: Sasha Levin <sashal@kernel.org>
To: Raul E Rangel <rrangel@chromium.org>
Cc: stable@vger.kernel.org, linux-mmc@vger.kernel.org,
djkurtz@google.com, adrian.hunter@intel.com,
zwisler@chromium.org, "Linus Walleij" <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org, "Chris Boot" <bootc@bootc.net>,
"Clément Péron" <peron.clem@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Ulf Hansson" <ulf.hansson@linaro.org>
Subject: Re: [stable/4.14.y PATCH 0/3] mmc: Fix a potential resource leak when shutting down request queue.
Date: Mon, 13 May 2019 20:43:06 -0400 [thread overview]
Message-ID: <20190514004306.GF11972@sasha-vm> (raw)
In-Reply-To: <20190513175521.84955-1-rrangel@chromium.org>
On Mon, May 13, 2019 at 11:55:18AM -0600, Raul E Rangel wrote:
>I think we should cherry-pick 41e3efd07d5a02c80f503e29d755aa1bbb4245de
>https://lore.kernel.org/patchwork/patch/856512/ into 4.14. It fixes a
>potential resource leak when shutting down the request queue.
>
>Once this patch is applied, there is a potential for a null pointer dereference.
>That's what the second patch fixes.
>
>The third patch is just an optimization to stop processing earlier.
Is this actually part of a fix? Why do we want this optimization?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-05-14 0:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 17:55 [stable/4.14.y PATCH 0/3] mmc: Fix a potential resource leak when shutting down request queue Raul E Rangel
2019-05-13 17:55 ` [stable/4.14.y PATCH 1/3] mmc: block: Simplify cleaning up the queue Raul E Rangel
2019-05-13 17:55 ` [stable/4.14.y PATCH 2/3] mmc: Fix null pointer dereference in mmc_init_request Raul E Rangel
2019-05-13 20:12 ` Greg KH
2019-05-13 17:55 ` [stable/4.14.y PATCH 3/3] mmc: Kill the request if the queuedata has been removed Raul E Rangel
2019-05-13 20:12 ` Greg KH
2019-05-14 0:43 ` Sasha Levin [this message]
2019-05-14 9:19 ` [stable/4.14.y PATCH 0/3] mmc: Fix a potential resource leak when shutting down request queue Greg Kroah-Hartman
2019-06-19 16:46 ` Raul Rangel
2019-06-19 17:09 ` Greg Kroah-Hartman
2019-06-19 18:23 ` Raul Rangel
2019-06-19 18:36 ` Greg Kroah-Hartman
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=20190514004306.GF11972@sasha-vm \
--to=sashal@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=bootc@bootc.net \
--cc=djkurtz@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=peron.clem@gmail.com \
--cc=rrangel@chromium.org \
--cc=stable@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=zwisler@chromium.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.