4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Guillaume Nault
[ Upstream commit 6b9f34239b00e6956a267abed2bc559ede556ad6 ]
l2tp_tunnel_create() inserts the new tunnel into the namespace's tunnel
list and sets the socket's ->sk_user_data
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Adrian Hunter
commit 117db4b27bf08dba412faf3924ba55fe970c57b8 upstream.
Overlap detection was not not updating the buffer's 'consecutive' flag.
Marking buffers consecutive has the advantage th
On Tue, 2018-04-17 at 17:31 +0200, Borislav Petkov wrote:
> On Tue, Apr 17, 2018 at 05:21:30PM +0200, Jörg Otte wrote:
> > finished bisection.
> > 39114b7a743e6759bab4d96b7d9651d44d17e3f9 is the first bad commit
> > (x86/pti: Never implicitly clear _PAGE_GLOBAL for kernel image).
>
> Looks like yo
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Huacai Chen
commit 7bbaf27d9c83037b6e60a818e57bdbedf6bc15be upstream.
Calling __stack_chk_guard_setup() in decompress_kernel() is too late
that stack checking always fails for decompress_kerne
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Phil Elwell
[ Upstream commit 4bfc33807a9a02764bdd1e42e794b3b401240f27 ]
lan78xx_read_otp tries to return -EINVAL in the event of invalid OTP
content, but the value gets overwritten before it
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Ming Lei
commit 0bca799b92807ee9be0890690f5dde7d8c6a8e25 upstream.
This patch orders getting budget and driver tag by making sure to acquire
driver tag after budget is got, this way can help t
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Ming Lei
commit bffa9909a6b48d8ca3398dec601bc9162a4020c4 upstream.
>From commit 4b855ad37194 ("blk-mq: Create hctx for each present CPU),
blk-mq doesn't remap queue after CPU topo is changed,
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Amir Goldstein
commit 3ec9b3fafcaf441cc4d46b9742cd6ec0c79f8df0 upstream.
As of now if we encounter an opaque dir while looking for a dentry, we set
d->last=true. This means that there is no ne
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Bill Kuzeja
commit 6d6340672ba3a99c4cf7af79c2edf7aa25595c84 upstream.
The code that fixes the crashes in the following commit introduced a small
memory leak:
commit 6a2cf8d3663e ("scsi: qla2x
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: J. Bruce Fields
commit 880a3a5325489a143269a8e172e7563ebf9897bc upstream.
We're neglecting to clear the umask after it's set, which can cause a
later unrelated rpc to (incorrectly) use the sam
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Simon Gaiser
commit 2a22ee6c3ab1d761bc9c04f1e4117edd55b82f09 upstream.
Commit fd8aa9095a95 ("xen: optimize xenbus driver for multiple
concurrent xenstore accesses") made a subtle change to the
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: John Johansen
commit 98cf5bbff413eadf1b9cb195a7b80cc61c72a50e upstream.
The existence test is not being properly logged as the signal mapping
maps it to the last entry in the named signal tabl
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: John Johansen
commit b5beb07ad32ab533027aa988d96a44965ec116f7 upstream.
Resource auditing is using the peer field which is not available
when the rlim data struct is used, because it is a diff
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Yazen Ghannam
commit e5d6a126d4c473499f354254a15ca0c2d8c84ca3 upstream.
Pass the bank number to smca_get_bank_type() since that's all we need.
Also, we should compare the bank number to MAX_N
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Williams
commit 8d0d8ed3356aa9ed43b819aaedd39b08ca453007 upstream.
Commit 1cf03c00e7c1 "nfit: scrub and register regions in a workqueue"
mistakenly attempts to register a region per BLK ap
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Julian Wiedmann
commit dae55b6fef58530c13df074bcc182c096609339e upstream.
Immediate retry of EQBS after CCQ 96 means that we potentially misreport
the state of buffers inspected during the fir
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Vasily Gorbik
commit 15deb080a6087b73089139569558965750e69d67 upstream.
When loadparm is set in reipl parm block, the kernel should also set
DIAG308_FLAGS_LP_VALID flag.
This fixes loadparm i
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry V. Levin
commit 9820e1c3376c641299624dd24646aed3167ad5b1 upstream.
Consistently use types provided by to fix the following
asm/bootparam.h userspace compilation errors:
/usr/i
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Yazen Ghannam
commit 27bd59502702fe51d9eb00450a75b727ec6bfcb4 upstream.
The block address is saved after the block is initialized when
threshold_init_device() is called.
Use the saved block a
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Li RongQing
commit a774635db5c430cbf21fa5d2f2df3d23aaa8e782 upstream.
The APIC ID as parsed from ACPI MADT is validity checked with the
apic->apic_id_valid() callback, which depends on the sel
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit bb5208b314c5127b716b2ee4f55803a8bb73b750 upstream.
Older devices with a serdev attached bcm bt hci, use an Interrupt ACPI
resource to describe the IRQ (rather then a GpioI
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Sudhir Sreedharan
commit 7972326a26b5bf8dc2adac575c4e03ee7e9d193a upstream.
This can be reproduced by bind/unbind the driver multiple times
in AM3517 board.
Analysis revealed that rtl8187_sta
4.16-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 30ce4d1903e1d8a7ccd110860a5eef3c638ed8be upstream.
missed it in "kill struct filename.separate" several years ago.
Cc: sta...@vger.kernel.org
Signed-off-by: Al Viro
Signed-off
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
commit 85ea29f19eab56ec16ec6b92bc67305998706afa upstream.
At put_v4l2_window32(), it tries to access kp->clips. However,
kp points to an userspace pointer. So, it should
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Helge Deller
commit d5654e156bc4d68a87bbaa6d7e020baceddf6e68 upstream.
Make sure that the HPMC (High Priority Machine Check) handler is 16-byte
aligned and that it's length in the IVT is a mul
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Dexuan Cui
commit 238064f13d057390a8c5e1a6a80f4f0a0ec46499 upstream.
The pci-hyperv driver's channel callback hv_pci_onchannelcallback() is not
really a hot path, so we don't need to mark it a
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Dexuan Cui
commit de0aa7b2f97d348ba7d1e17a00744c989baa0cb6 upstream.
1. With the patch "x86/vector/msi: Switch to global reservation mode",
the recent v4.15 and newer kernels always hang for 1
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Prashant Bhole
commit 621b6d2ea297d0fb6030452c5bcd221f12165fcf upstream.
A use-after-free bug was caught by KASAN while running usdt related
code (BCC project. bcc/tests/python/test_usdt2.py):
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Yazen Ghannam
commit 27bd59502702fe51d9eb00450a75b727ec6bfcb4 upstream.
The block address is saved after the block is initialized when
threshold_init_device() is called.
Use the saved block a
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Li RongQing
commit a774635db5c430cbf21fa5d2f2df3d23aaa8e782 upstream.
The APIC ID as parsed from ACPI MADT is validity checked with the
apic->apic_id_valid() callback, which depends on the sel
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Yunlong Song
commit b94929d975c8423defc9aededb0f499ff936b509 upstream.
Commit 7a20b8a61eff81bdb7097a578752a74860e9d142 ("f2fs: allocate node
and hot data in the beginning of partition") introd
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Keith Busch
commit 2079699c10c8c60a9572540c2f77d045abf036eb upstream.
If a task is holding a reference to a namespace on a removed controller,
the head will not be released. If the same contro
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit 818e0fa293ca836eba515615c64680ea916fd7cd upstream.
scsi_device_quiesce() uses synchronize_rcu() to guarantee that the
effect of blk_set_preempt_only() will be visible fo
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Kravetz
commit 5df63c2a149ae65a9ec239e7c2af44efa6f79beb upstream.
This is a fix for a regression in 32 bit kernels caused by an invalid
check for pgoff overflow in hugetlbfs mmap setup.
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Auger
[ Upstream commit 7ced6c98c7ab7a1f6743931e28671b833af79b1e ]
vhost_copy_to_user is used to copy vring used elements to userspace.
We should use VHOST_ADDR_USED instead of VHOST_ADD
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Phil Elwell
[ Upstream commit 4bfc33807a9a02764bdd1e42e794b3b401240f27 ]
lan78xx_read_otp tries to return -EINVAL in the event of invalid OTP
content, but the value gets overwritten before it
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Michael S. Tsirkin
commit c61611f70958d86f659bca25c02ae69413747a8d upstream.
get_user_pages_fast is supposed to be a faster drop-in equivalent of
get_user_pages. As such, callers expect it to
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Amir Goldstein
commit 9f99e50d460ac7fd5f6c9b97aad0088c28c8656d upstream.
For broken hardlinks, we do not return lower st_ino, so we should
also not return lower pseudo st_dev.
Fixes: a0c5ad30
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit bb5208b314c5127b716b2ee4f55803a8bb73b750 upstream.
Older devices with a serdev attached bcm bt hci, use an Interrupt ACPI
resource to describe the IRQ (rather then a GpioI
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Vasily Gorbik
commit 15deb080a6087b73089139569558965750e69d67 upstream.
When loadparm is set in reipl parm block, the kernel should also set
DIAG308_FLAGS_LP_VALID flag.
This fixes loadparm i
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Helge Deller
commit d5654e156bc4d68a87bbaa6d7e020baceddf6e68 upstream.
Make sure that the HPMC (High Priority Machine Check) handler is 16-byte
aligned and that it's length in the IVT is a mul
4.15-stable review patch. If anyone has any objections, please let me know.
--
From: Szymon Janc
commit 082f2300cfa1a3d9d5221c38c5eba85d4ab98bd8 upstream.
Local random address needs to be updated before creating connection if
RPA from LE Direct Advertising Report was resolved
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Adrian Hunter
commit 91d29b288aed3406caf7c454bf2b898c96cfd177 upstream.
timestamp_insn_cnt is used to estimate the timestamp based on the number of
instructions since the last known timestamp.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Yazen Ghannam
commit 11cf887728a3d1de77cc12ce247b64ef32608891 upstream.
Scalable MCA systems have various types of banks. The bank's type
can determine how we handle errors from it. For exampl
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Adrian Hunter
commit 117db4b27bf08dba412faf3924ba55fe970c57b8 upstream.
Overlap detection was not not updating the buffer's 'consecutive' flag.
Marking buffers consecutive has the advantage th
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Phil Elwell
[ Upstream commit 4bfc33807a9a02764bdd1e42e794b3b401240f27 ]
lan78xx_read_otp tries to return -EINVAL in the event of invalid OTP
content, but the value gets overwritten before it
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sudhir Sreedharan
commit 7972326a26b5bf8dc2adac575c4e03ee7e9d193a upstream.
This can be reproduced by bind/unbind the driver multiple times
in AM3517 board.
Analysis revealed that rtl8187_sta
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Yazen Ghannam
commit 68627a697c195937672ce07683094c72b1174786 upstream.
Currently, bank 4 is reserved on Fam17h, so we chose not to initialize
bank 4 in the smca_banks array. This means that w
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
commit 85ea29f19eab56ec16ec6b92bc67305998706afa upstream.
At put_v4l2_window32(), it tries to access kp->clips. However,
kp points to an userspace pointer. So, it should
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Yazen Ghannam
commit c6708d50f166bea2d763c96485d31fdbc50204f1 upstream.
The MCA_STATUS[ErrorCodeExt] field is very bank type specific.
We currently check if the ErrorCodeExt value is 0x0 or 0x
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit f3aefb6a7066e24bfea7fcf1b07907576de69d63 upstream.
make_checksum_hmac_md5() is allocating an HMAC transform and doing
crypto API calls in the following order:
crypto_a
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Amir Goldstein
commit 3ec9b3fafcaf441cc4d46b9742cd6ec0c79f8df0 upstream.
As of now if we encounter an opaque dir while looking for a dentry, we set
d->last=true. This means that there is no ne
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: J. Bruce Fields
commit 880a3a5325489a143269a8e172e7563ebf9897bc upstream.
We're neglecting to clear the umask after it's set, which can cause a
later unrelated rpc to (incorrectly) use the sam
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 30ce4d1903e1d8a7ccd110860a5eef3c638ed8be upstream.
missed it in "kill struct filename.separate" several years ago.
Cc: sta...@vger.kernel.org
Signed-off-by: Al Viro
Signed-off
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Szymon Janc
commit 082f2300cfa1a3d9d5221c38c5eba85d4ab98bd8 upstream.
Local random address needs to be updated before creating connection if
RPA from LE Direct Advertising Report was resolved
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
commit 85ea29f19eab56ec16ec6b92bc67305998706afa upstream.
At put_v4l2_window32(), it tries to access kp->clips. However,
kp points to an userspace pointer. So, it should b
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Will Deacon
commit f71c2ffcb20dd8626880747557014bb9a61eb90e upstream.
Like we've done for get_user and put_user, ensure that user pointers
are masked before invoking the u
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Will Deacon
commit d68e3ba5303f7e1099f51fdcd155f5263da8569b upstream.
Entry into recent versions of ARM Trusted Firmware will invalidate the CPU
branch predictor state in
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Suzuki K Poulose
commit 55b35d070c2534dfb714b883f3c3ae05d02032da upstream.
When a CPU is brought up after we have finalised the system
wide capabilities (i.e, features and
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Marc Zyngier
commit a8e4c0a919ae310944ed2c9ace11cf3ccd8a609b upstream.
We call arm64_apply_bp_hardening() from post_ttbr_update_workaround,
which has the unexpected conseq
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Will Deacon
commit 0f15adbb2861ce6f75ccfc5a92b19eae0ef327d0 upstream.
Aliasing attacks against CPU branch predictors can allow an attacker to
redirect speculative control
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Adrian Hunter
commit 117db4b27bf08dba412faf3924ba55fe970c57b8 upstream.
Overlap detection was not not updating the buffer's 'consecutive' flag.
Marking buffers consecutive has the advantage tha
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Marc Zyngier
commit e78eef554a912ef6c1e0bbf97619dafbeae3339f upstream.
Since PSCI 1.0 allows the SMCCC version to be (indirectly) probed,
let's do that at boot time, and e
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Marc Zyngier
commit 6167ec5c9145cdf493722dfd80a5d48bafc4a18a upstream.
A new feature of SMCCC 1.1 is that it offers firmware-based CPU
workarounds. In particular, SMCCC_AR
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Marc Zyngier
commit 06f1494f837da8997d670a1ba87add7963b08922 upstream.
Some minor erratum may not be fixed in further revisions of a core,
leading to a situation where the
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Marc Zyngier
commit ded4c39e93f3b72968fdb79baba27f3b83dad34c upstream.
Function identifiers are a 32bit, unsigned quantity. But we never
tell so to the compiler, resulting
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Adrian Hunter
commit 91d29b288aed3406caf7c454bf2b898c96cfd177 upstream.
timestamp_insn_cnt is used to estimate the timestamp based on the number of
instructions since the last known timestamp.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Szymon Janc
commit 082f2300cfa1a3d9d5221c38c5eba85d4ab98bd8 upstream.
Local random address needs to be updated before creating connection if
RPA from LE Direct Advertising Report was resolved i
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Williams
commit 8d0d8ed3356aa9ed43b819aaedd39b08ca453007 upstream.
Commit 1cf03c00e7c1 "nfit: scrub and register regions in a workqueue"
mistakenly attempts to register a region per BLK ape
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Will Deacon
commit aa6acde65e03186b5add8151e1ffe36c3c62639b upstream.
Cortex-A57, A72, A73 and A75 are susceptible to branch predictor aliasing
and can theoretically be at
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit f3aefb6a7066e24bfea7fcf1b07907576de69d63 upstream.
make_checksum_hmac_md5() is allocating an HMAC transform and doing
crypto API calls in the following order:
crypto_ah
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Marc Zyngier
commit f2d3b2e8759a5833df6f022e42df2d581e6d843c upstream.
One of the major improvement of SMCCC v1.1 is that it only clobbers
the first 4 registers, both on 3
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 30ce4d1903e1d8a7ccd110860a5eef3c638ed8be upstream.
missed it in "kill struct filename.separate" several years ago.
Cc: sta...@vger.kernel.org
Signed-off-by: Al Viro
Signed-off-
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Bassem Boubaker
[ Upstream commit 53765341ee821c0a0f1dec41adc89c9096ad694c ]
The Cinterion AHS8 is a 3G device with one embedded WWAN interface
using cdc_ether as a driver.
The modem is contr
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Stefan Hajnoczi
[ Upstream commit d14d2b78090c7de0557362b26a4ca591aa6a9faa ]
Commit d65026c6c62e7d9616c8ceb5a53b68bcdc050525 ("vhost: validate log
when IOTLB is enabled") introduced a regressi
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Julian Wiedmann
commit 0cf1e05157b9e5530dcc3ca9fec9bf617fc93375 upstream.
On an Output queue, both EMPTY and PENDING buffer states imply that the
buffer is ready for completion-processing by th
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Marc Zyngier
commit f5115e8869e1dfafac0e414b4f1664f3a84a4683 upstream.
When handling an SMC trap, the "preferred return address" is set
to that of the SMC, and not the nex
On Tue, Apr 17, 2018 at 09:21:45PM +0530, Vijendar Mukunda wrote:
> On ST/CZ based platforms, for specific platform bt uart
> mux to be defined for bt i2s.
Please don't send isolated patches numbered like they're in a series,
the numbering is only there so people know what order a series should be
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Will Deacon
commit a65d219fe5dc7887fd5ca04c2ac3e9a34feb8dfc upstream.
Hook up MIDR values for the Cortex-A72 and Cortex-A75 CPUs, since they
will soon need MIDR matches fo
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Marc Zyngier
commit 58e0b2239a4d997094ba63986ef4de29ddc91d87 upstream.
PSCI 1.0 can be trivially implemented by providing the FEATURES
call on top of PSCI 0.2 and returnin
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Marc Zyngier
commit 09e6be12effdb33bf7210c8867bbd213b66a499e upstream.
The new SMC Calling Convention (v1.1) allows for a reduced overhead
when calling into the firmware,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Marc Zyngier
commit 84684fecd7ea381824a96634a027b7719587fb77 upstream.
Instead of open coding the accesses to the various registers,
let's add explicit SMCCC accessors.
R
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Will Deacon
commit 669474e772b952b14f4de4845a1558fd4c0414a4 upstream.
For CPUs capable of data value prediction, CSDB waits for any outstanding
predictions to architectura
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Marc Zyngier
commit d0a144f12a7ca8368933eae6583c096c363ec506 upstream.
As we're about to trigger a PSCI version explosion, it doesn't
hurt to introduce a PSCI_VERSION help
From: Borislav Petkov
Hi,
here's v3 now that the merge window is done, with hopefully all review
feedback (thanks Josh et al!) incorporated.
Thx.
Borislav Petkov (9):
x86/dumpstack: Remove code_bytes
x86/dumpstack: Unexport oops_begin()
x86/dumpstack: Carve out Code: dumping into a funct
On 04/16/2018 10:51 AM, Halil Pasic wrote:
On 04/16/2018 03:05 PM, Pierre Morel wrote:
+static void vfio_ap_mdev_release(struct mdev_device *mdev)
+{
+struct ap_matrix_mdev *matrix_mdev = mdev_get_drvdata(mdev);
+
+kvm_ap_deconfigure_matrix(matrix_mdev->kvm);
+kvm_ap_interpret_instr
From: Borislav Petkov
No functionality change, carve it out into a separate function for later
changes.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/dumpstack.c | 57 -
1 file changed, 30 insertions(+), 27 deletions(-)
diff --git a/arch/x86/ke
From: Borislav Petkov
This was added by
86c418374223 ("[PATCH] i386: add option to show more code in oops reports")
long time ago but experience shows that 64 instruction bytes are plenty
when deciphering an oops. So get rid of it.
Removing it will simplify further enhancements to the opcode
From: Borislav Petkov
The only user outside of arch/ is not a module since
86cd47334b00 ("ACPI, APEI, GHES, Prevent GHES to be built as module")
No functional changes.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/dumpstack.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/x86
From: Borislav Petkov
The code used to iterate byte-by-byte over the bytes around RIP and that
is expensive: disabling pagefaults around it, copy_from_user, etc...
Make it read the whole buffer of OPCODE_BUFSIZE size in one go. Use a
statically allocated 64 bytes buffer so that concurrent show_o
From: Borislav Petkov
Save the regs set when we call __die() for the first time and print it
in oops_end().
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/dumpstack.c | 32
1 file changed, 12 insertions(+), 20 deletions(-)
diff --git a/arch/x86/kernel/dump
From: Borislav Petkov
Will be used in the next patch.
Signed-off-by: Borislav Petkov
---
arch/x86/include/asm/stacktrace.h | 1 +
arch/x86/kernel/dumpstack.c | 6 +++---
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/arch/x86/include/asm/stacktrace.h
b/arch/x86/include/a
From: Borislav Petkov
... which shows the Instruction Pointer along with the insn bytes around
it. Use it whenever we print rIP. Drop the rIP < PAGE_OFFSET check since
our probe_kernel_read() can handle any address properly.
Signed-off-by: Borislav Petkov
---
arch/x86/include/asm/stacktrace.h
On 17/04/2018 17:02, Tony Krowiak wrote:
On 04/16/2018 06:51 AM, Pierre Morel wrote:
On 15/04/2018 23:22, Tony Krowiak wrote:
The VFIO AP device model exploits interpretive execution of AP
instructions (APIE) to provide guests passthrough access to AP
devices. This patch introduces a new interf
From: Borislav Petkov
Sometimes it is useful to see which user opcode bytes RIP points to
when a fault happens: be it to rule out RIP corruption, to dump info
early during boot, when doing core dumps is impossible due to not having
writable fs yet.
Sometimes it is useful if debugging an issue an
From: Borislav Petkov
The whole reasoning behind the amount of opcode bytes dumped and
prologue length isn't very clear so let's hold down some of the reasons
for why it is done the way it is.
Signed-off-by: Borislav Petkov
---
arch/x86/kernel/dumpstack.c | 19 +++
1 file chang
On 04/16/2018 09:13 AM, Pierre Morel wrote:
On 15/04/2018 23:22, Tony Krowiak wrote:
This patch provides documentation describing the AP architecture and
design concepts behind the virtualization of AP devices. It also
includes an example of how to configure AP devices for exclusive
use of KVM g
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Phil Elwell
[ Upstream commit 4bfc33807a9a02764bdd1e42e794b3b401240f27 ]
lan78xx_read_otp tries to return -EINVAL in the event of invalid OTP
content, but the value gets overwritten before it
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mark Rutland
From: Marc Zyngier
commit 1a2fb94e6a771ff94f4afa22497a4695187b820c upstream.
As we're about to update the PSCI support, and because I'm lazy,
let's move the PSCI include file to
On Tue, Apr 17, 2018 at 09:14:32PM +0530, Souptick Joarder wrote:
> Not exactly. The plan for these patches is to introduce new vm_fault_t type
> in vm_operations_struct fault handlers. It's now available in 4.17-rc1. We
> will
> push all the required drivers/filesystem changes through different m
601 - 700 of 1264 matches
Mail list logo