From: Borislav Petkov <bp@alien8.de>
To: Robert Richter <rrichter@marvell.com>,
John Garry <john.garry@huawei.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Tony Luck <tony.luck@intel.com>,
James Morse <james.morse@arm.com>,
Aristeu Rozanski <aris@redhat.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] EDAC/mc: Fixes for mci device removal
Date: Thu, 13 Feb 2020 12:05:12 +0100 [thread overview]
Message-ID: <20200213110512.GH31799@zn.tnic> (raw)
In-Reply-To: <20200212120340.4764-1-rrichter@marvell.com>
On Wed, Feb 12, 2020 at 01:03:36PM +0100, Robert Richter wrote:
> This series is a split of
>
> [v2] EDAC/mc: Fix use-after-free and memleaks during device removal
> https://lore.kernel.org/patchwork/patch/1190002/
>
> in smaller patches to better handle stable backports.
>
> Patch #1 helps to ease backports of patch #2 to 5.3 and earlier
> kernels, see patch descriptions of both for details.
>
> Patch #2 is the smallest possible fix to address use-after-free and
> memleak issues aimed for backports.
>
> Patch #3 is another small patch that is split off for stable. This
> fixes code already commited to stable trees.
>
> Patch #4 is the all remaining code containing the rework of the mci
> device removal. Resulting code is the same as in v2 except for the
> changes outlined for v3:
>
> v3:
> * split patch into smaller pieces to ease backports,
> * removed edac_remove_sysfs_mci_device() in edac_mc_free(), at this
> point the mci device is always unregistered
>
> Robert Richter (4):
> Revert parts of "EDAC/mc_sysfs: Make debug messages consistent"
> EDAC/mc: Fix use-after-free and memleaks during device removal
> EDAC/sysfs: Remove csrow objects on errors
> EDAC/mc: Change mci device removal to use put_device()
>
> drivers/edac/edac_mc.c | 20 +++----
> drivers/edac/edac_mc_sysfs.c | 100 +++++++++++++----------------------
> drivers/edac/edac_module.h | 1 -
> 3 files changed, 48 insertions(+), 73 deletions(-)
Thanks, first three (1+2 squashed) pushed here:
https://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git/log/?h=edac-urgent
@John: if you could run them one more time on your machines, that would
be great!
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-02-13 11:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 12:03 [PATCH v3 0/4] EDAC/mc: Fixes for mci device removal Robert Richter
2020-02-12 12:03 ` [PATCH v3 1/4] Revert parts of "EDAC/mc_sysfs: Make debug messages consistent" Robert Richter
2020-02-12 12:03 ` [PATCH v3 2/4] EDAC/mc: Fix use-after-free and memleaks during device removal Robert Richter
2020-02-12 12:03 ` [PATCH v3 3/4] EDAC/sysfs: Remove csrow objects on errors Robert Richter
2020-02-12 12:03 ` [PATCH v3 4/4] EDAC/mc: Change mci device removal to use put_device() Robert Richter
2020-02-13 11:05 ` Borislav Petkov [this message]
2020-02-13 11:10 ` [PATCH v3 0/4] EDAC/mc: Fixes for mci device removal John Garry
2020-02-13 12:08 ` John Garry
2020-02-13 12:28 ` Borislav Petkov
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=20200213110512.GH31799@zn.tnic \
--to=bp@alien8.de \
--cc=aris@redhat.com \
--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=rrichter@marvell.com \
--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