From: Robert Richter <rrichter@marvell.com>
To: Borislav Petkov <bp@alien8.de>
Cc: John Garry <john.garry@huawei.com>,
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 13:28:52 +0000 [thread overview]
Message-ID: <20191218132843.vur4tpviv2alpaaq@rric.localdomain> (raw)
In-Reply-To: <20191218130510.GF24886@zn.tnic>
On 18.12.19 14:05:10, Borislav Petkov wrote:
> 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
> > confusion.
>
> 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.
I am fine with taking the time. Once it hits upstream it can be
backported to stable. There is a small conflict with 5.4, so it will
need some manual tweaking anyway.
>
> Also, how does this patch play with your cleanup? I'm guessing this
> patch goes first and then the cleanup...
Right, the fix will be first. I have already a rebase of the cleanup
series and can send a v3 as soon as this fix is applied to a tree.
-Robert
next prev parent reply other threads:[~2019-12-18 13:29 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
2019-12-18 13:28 ` Robert Richter [this message]
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=20191218132843.vur4tpviv2alpaaq@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).