From: Borislav Petkov <email@example.com>
To: Robert Richter <firstname.lastname@example.org>
Cc: John Garry <email@example.com>,
Mauro Carvalho Chehab <firstname.lastname@example.org>,
Tony Luck <email@example.com>,
James Morse <firstname.lastname@example.org>,
Subject: Re: [PATCH] EDAC/mc: Fix use-after-free and memleaks during device removal
Date: Wed, 18 Dec 2019 14:05:10 +0100 [thread overview]
Message-ID: <20191218130510.GF24886@zn.tnic> (raw)
On Wed, Dec 18, 2019 at 12:55:04PM +0000, Robert Richter wrote:
> 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
I haven't looked at it yet but I'd prefer if this patch went the normal
way and landed in stable only eventually so that it gets some testing by
people in linux-next first.
It is not a trivial patch and we did break EDAC with recent rework so
I'd prefer if we take it slowly here and do more extensive testing
before we expose it to the world.
Also, how does this patch play with your cleanup? I'm guessing this
patch goes first and then the cleanup...
next prev parent reply other threads:[~2019-12-18 13:05 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
2019-12-18 13:05 ` Borislav Petkov [this message]
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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).