From: Robert Richter <rrichter@marvell.com>
To: John Garry <john.garry@huawei.com>
Cc: Borislav Petkov <bp@alien8.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Tony Luck <tony.luck@intel.com>,
James Morse <james.morse@arm.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] EDAC/mc: Fix use-after-free and memleaks during device removal
Date: Wed, 18 Dec 2019 12:55:04 +0000 [thread overview]
Message-ID: <20191218125456.kkqfuq7crshwwc7q@rric.localdomain> (raw)
In-Reply-To: <0c7da2d7-1cab-f518-2309-f740d7ef36fa@huawei.com>
On 18.12.19 11:28:25, John Garry wrote:
> On 18/12/2019 06:22, Robert Richter wrote:
> > The patch has been tested with the above kernel options, no issues
> > seen any longer.
> >
> > This patch should be marked as stable.
>
> Not sure why you haven't...
I leave that to the maintainer as he is editing the SOB chain anyway.
The patch would be sent to the stable list already which may cause
confusion.
>
> >
> > Reported-by: John Garry <john.garry@huawei.com>
>
> The splats and leaks have disappeared for when booting my arm64 machine:
> Tested-by: John Garry <john.garry@huawei.com>
Thanks for testing.
-Robert
next prev parent reply other threads:[~2019-12-18 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 6:22 [PATCH] EDAC/mc: Fix use-after-free and memleaks during device removal Robert Richter
2019-12-18 11:28 ` John Garry
2019-12-18 12:55 ` Robert Richter [this message]
2019-12-18 13:05 ` Borislav Petkov
2019-12-18 13:28 ` Robert Richter
2019-12-22 12:15 ` Borislav Petkov
2019-12-22 17:22 ` Robert Richter
2020-01-21 18:13 ` Aristeu Rozanski
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=20191218125456.kkqfuq7crshwwc7q@rric.localdomain \
--to=rrichter@marvell.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=john.garry@huawei.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=tony.luck@intel.com \
/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).