[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190514004306.GF11972@sasha-vm>
Date: Mon, 13 May 2019 20:43:06 -0400
From: Sasha Levin <sashal@...nel.org>
To: Raul E Rangel <rrangel@...omium.org>
Cc: stable@...r.kernel.org, linux-mmc@...r.kernel.org,
djkurtz@...gle.com, adrian.hunter@...el.com, zwisler@...omium.org,
Linus Walleij <linus.walleij@...aro.org>,
linux-kernel@...r.kernel.org, Chris Boot <bootc@...tc.net>,
Clément Péron <peron.clem@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [stable/4.14.y PATCH 0/3] mmc: Fix a potential resource leak
when shutting down request queue.
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
Powered by blists - more mailing lists