From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [PATCH v3 0/9] stm/intel_th: Updates for 4.4
Date: Tue, 22 Dec 2015 17:25:14 +0200 [thread overview]
Message-ID: <1450797923-23072-1-git-send-email-alexander.shishkin@linux.intel.com> (raw)
Hi Greg,
Since the previous versions ([1], [2]) didn't land anywhere yet, I'm
resending the whole thing with a few additions: Sasha reported a
user-controllable allocation with a possible overflow, Chunyan found
an off-by-one in another allocation path and I also found a couple of
locking issues that are better resolved sooner than later. Please
consider this for 4.4 still if possible.
[1] http://marc.info/?l=linux-kernel&m=144845503811729
[2] http://marc.info/?l=linux-kernel&m=144706387705997
Alexander Shishkin (5):
stm class: Fix locking in unbinding policy path
stm class: Fix link list locking
stm class: Prevent user-controllable allocations
intel_th: pci: Add Apollo Lake SOC support
intel_th: pci: Add Broxton SOC support
Arnd Bergmann (1):
stm class: Select CONFIG_SRCU
Chunyan Zhang (1):
stm class: Fix an off-by-one in master array allocation
Geert Uytterhoeven (2):
stm class: Hide STM-specific options if STM is disabled
intel_th: INTEL_TH should depend on HAS_DMA
drivers/hwtracing/intel_th/Kconfig | 1 +
drivers/hwtracing/intel_th/pci.c | 10 +++++++++
drivers/hwtracing/stm/Kconfig | 5 +++++
drivers/hwtracing/stm/core.c | 43 +++++++++++++++++++++++++++++---------
drivers/hwtracing/stm/policy.c | 18 +++++++++++++---
drivers/hwtracing/stm/stm.h | 1 +
6 files changed, 65 insertions(+), 13 deletions(-)
--
2.6.4
next reply other threads:[~2015-12-22 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 15:25 Alexander Shishkin [this message]
2015-12-22 15:25 ` [PATCH v3 1/9] stm class: Hide STM-specific options if STM is disabled Alexander Shishkin
2015-12-22 15:25 ` [PATCH v3 2/9] intel_th: INTEL_TH should depend on HAS_DMA Alexander Shishkin
2015-12-22 15:25 ` [PATCH v3 3/9] stm class: Select CONFIG_SRCU Alexander Shishkin
2015-12-22 15:25 ` [PATCH v3 4/9] stm class: Fix locking in unbinding policy path Alexander Shishkin
2015-12-22 15:25 ` [PATCH v3 5/9] stm class: Fix link list locking Alexander Shishkin
2015-12-22 15:25 ` [PATCH v3 6/9] stm class: Fix an off-by-one in master array allocation Alexander Shishkin
2015-12-22 15:25 ` [PATCH v3 7/9] stm class: Prevent user-controllable allocations Alexander Shishkin
2015-12-22 15:25 ` [PATCH v3 8/9] intel_th: pci: Add Apollo Lake SOC support Alexander Shishkin
2015-12-22 15:25 ` [PATCH v3 9/9] intel_th: pci: Add Broxton " Alexander Shishkin
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=1450797923-23072-1-git-send-email-alexander.shishkin@linux.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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®