From: Sasha Levin <sashal@kernel.org>
To: Xiaochen Shen <xiaochen.shen@intel.com>
Cc: stable@vger.kernel.org, gregkh@linuxfoundation.org,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
hpa@zytor.com, tony.luck@intel.com, fenghua.yu@intel.com,
reinette.chatre@intel.com, x86@kernel.org,
linux-kernel@vger.kernel.org, pei.p.jia@intel.com,
Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH 4.19 1/3] x86/resctrl: Fix use-after-free when deleting resource groups
Date: Sun, 2 Feb 2020 16:56:41 -0500 [thread overview]
Message-ID: <20200202215641.GB1732@sasha-vm> (raw)
In-Reply-To: <1580594537-2972-1-git-send-email-xiaochen.shen@intel.com>
On Sun, Feb 02, 2020 at 06:02:17AM +0800, Xiaochen Shen wrote:
>commit b8511ccc75c033f6d54188ea4df7bf1e85778740 upstream.
>
>A resource group (rdtgrp) contains a reference count (rdtgrp->waitcount)
>that indicates how many waiters expect this rdtgrp to exist. Waiters
>could be waiting on rdtgroup_mutex or some work sitting on a task's
>workqueue for when the task returns from kernel mode or exits.
I've queued up the 4.19 and 4.14 backports, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2020-02-02 21:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 16:28 [PATCH 0/4] Fix use-after-free and deadlock issues Xiaochen Shen
2020-01-08 16:28 ` [PATCH 1/4] x86/resctrl: Fix use-after-free when deleting resource groups Xiaochen Shen
[not found] ` <20200109143629.C6C822077B@mail.kernel.org>
2020-01-14 8:51 ` Xiaochen Shen
2020-01-20 16:47 ` [tip: x86/urgent] " tip-bot2 for Xiaochen Shen
2020-01-08 16:28 ` [PATCH 2/4] x86/resctrl: Fix use-after-free due to inaccurate refcount of rdtgroup Xiaochen Shen
[not found] ` <20200109143631.EF0A42077C@mail.kernel.org>
2020-01-14 9:13 ` Xiaochen Shen
2020-01-20 16:47 ` [tip: x86/urgent] " tip-bot2 for Xiaochen Shen
2020-01-08 16:28 ` [PATCH 3/4] x86/resctrl: Fix a deadlock due to inaccurate active reference of kernfs node Xiaochen Shen
[not found] ` <20200109143630.DD673206ED@mail.kernel.org>
2020-01-14 9:17 ` Xiaochen Shen
2020-01-20 16:47 ` [tip: x86/urgent] x86/resctrl: Fix a deadlock due to inaccurate reference tip-bot2 for Xiaochen Shen
2020-01-08 16:28 ` [PATCH 4/4] x86/resctrl: Clean up unused function parameter in mkdir path Xiaochen Shen
2020-01-20 16:47 ` [tip: x86/urgent] " tip-bot2 for Xiaochen Shen
2020-02-01 21:59 ` [PATCH 4.14 1/3] x86/resctrl: Fix use-after-free when deleting resource groups Xiaochen Shen
2020-02-01 22:00 ` [PATCH 4.14 2/3] x86/resctrl: Fix use-after-free due to inaccurate refcount of rdtgroup Xiaochen Shen
2020-02-01 22:00 ` [PATCH 4.14 3/3] x86/resctrl: Fix a deadlock due to inaccurate reference Xiaochen Shen
2020-02-01 22:02 ` [PATCH 4.19 1/3] x86/resctrl: Fix use-after-free when deleting resource groups Xiaochen Shen
2020-02-02 21:56 ` Sasha Levin [this message]
2020-02-01 22:03 ` [PATCH 4.19 2/3] x86/resctrl: Fix use-after-free due to inaccurate refcount of rdtgroup Xiaochen Shen
2020-02-01 22:04 ` [PATCH 4.19 3/3] x86/resctrl: Fix a deadlock due to inaccurate reference Xiaochen Shen
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=20200202215641.GB1732@sasha-vm \
--to=sashal@kernel.org \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=fenghua.yu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pei.p.jia@intel.com \
--cc=reinette.chatre@intel.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=xiaochen.shen@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
all inboxes | Powered by JetHome®