From: Richard Weinberger <richard@nod.at>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] UBI: Fix double free after do_sync_erase()
Date: Fri, 07 Nov 2014 12:53:04 +0100 [thread overview]
Message-ID: <545CB2A0.8050504@nod.at> (raw)
In-Reply-To: <1415361043.958.326.camel@sauron.fi.intel.com>
Am 07.11.2014 um 12:50 schrieb Artem Bityutskiy:
> On Thu, 2014-11-06 at 16:47 +0100, Richard Weinberger wrote:
>> If the erase worker is unable to erase a PEB it will
>> free the ubi_wl_entry itself.
>> The failing ubi_wl_entry must not free()'d again after
>> do_sync_erase() returns.
>>
>> Cc: <stable@vger.kernel.org>
>> Signed-off-by: Richard Weinberger <richard@nod.at>
>
> Pushed, thanks!
BTW: Please don't forget "[PATCH] UBI: Fix invalid vfree()".
Thanks,
//richard
prev parent reply other threads:[~2014-11-07 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 15:47 [PATCH] UBI: Fix double free after do_sync_erase() Richard Weinberger
2014-11-07 11:50 ` Artem Bityutskiy
2014-11-07 11:53 ` Richard Weinberger [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=545CB2A0.8050504@nod.at \
--to=richard@nod.at \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).