linux-kernel - Re: [PATCH] EDAC/mc: Fix use-after-free and memleaks during device removal

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20191218132843.vur4tpviv2alpaaq@rric.localdomain>
Date:   Wed, 18 Dec 2019 13:28:52 +0000
From:   Robert Richter <rrichter@...vell.com>
To:     Borislav Petkov <bp@...en8.de>
CC:     John Garry <john.garry@...wei.com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Tony Luck <tony.luck@...el.com>,
        James Morse <james.morse@....com>,
        "linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] EDAC/mc: Fix use-after-free and memleaks during device
 removal

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