Hi Jun,
2018-03-12 13:58 GMT+08:00 Jun Li :
> Hi
>> -Original Message-
>> From: 李書帆 [mailto:leechu...@gmail.com]
>> Sent: 2018年3月12日 13:22
>> To: Jun Li
>> Cc: Greg Kroah-Hartman ;
>> heikki.kroge...@linux.intel.com; li...@roeck-us.net; g...@kroah.com;
>> shufan_...@richtek.com; cy_hu...@
On 3/11/18 10:03 AM, Colin King wrote:
From: Colin Ian King
Functions rds_info_from_znotifier and rds_message_zcopy_from_user are
local to the source and do not need to be in global scope, so make them
static.
Cleans up sparse warnins:
net/rds/message.c:70:27: warning: symbol 'rds_info_from_zn
On 3/11/18 9:27 AM, Colin King wrote:
From: Colin Ian King
Variable sg_off is assigned a value but it is never read, hence it is
redundant and can be removed.
Cleans up clang warning:
net/rds/message.c:373:2: warning: Value stored to 'sg_off' is never read
Signed-off-by: Colin Ian King
---
On Mon, 12 Mar 2018, Jason Vas Dias wrote:
checkpatch.pl still reports:
total: 15 errors, 3 warnings, 165 lines checked
> +notrace static u64 vread_tsc_raw(void)
> +{
> + u64 tsc, last=gtod->raw_cycle_last;
> + if( likely( gtod->has_rdtscp ) )
> + tsc = rdtscp((void*)0
Read CommonLPIAff from GICR_TYPER and check whether the
values are same in each register. If they are different,
prints warning message and set CommonLPIAff to zero.
Signed-off-by: Yang Yingliang
---
drivers/irqchip/irq-gic-v3.c | 20
include/linux/irqchip/arm-gic-v3.h
The config of LPIs need to be same in each prop_page.
So if one prop_page is modified, other prop_page should
be updated too.
Signed-off-by: Yang Yingliang
---
drivers/irqchip/irq-gic-v3-its.c | 39 ++-
1 file changed, 30 insertions(+), 9 deletions(-)
diff --
Change prop_page to per-cpu type and add its_cpu_allocate_prop_tables()
to allocate LPI property tables. This function is called by each oneline
cpu and allocate tables according to the value of CommonLPIAff.
The spec defines the field:
CommonLPIAff, bits [25:24]
The affinity level at which
Use alloc_pages_node() to allocate pages on current node.
Signed-off-by: Yang Yingliang
---
drivers/irqchip/irq-gic-v3-its.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
index a03e18e..4ebe131 100
This patch set adjust struct rdists to support CommonLPIAff field.
This field is described in spec:
CommonLPIAff, bits [25:24]
The affinity level at which Redistributors share a LPI Configuration table.
00 All Redistributors must share a LPI Configuration table.
01 All Redistributors with the same
Hi Jason,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v4.16-rc4]
url:
https://github.com/0day-ci/linux/commits/Jason-Vas-Dias/x86-vdso-on-Intel-VDSO-should-handle-CLOCK_MONOTONIC_RAW/20180312-141707
config: x86_64-randconfig-x002-201810 (attached as .config)
Audit link denied events emit disjointed records when audit is disabled.
No records should be emitted when audit is disabled.
See: https://github.com/linux-audit/audit-kernel/issues/21
Signed-off-by: Richard Guy Briggs
---
kernel/audit.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/ker
Audit link denied events were being unexpectedly produced in a disjoint
way when audit was disabled, and when they were expected, there were
duplicate PATH records. This patchset addresses both issues for
symlinks and hardlinks.
This was introduced with
commit b24a30a7305418ff138ff51776fc
Hi Jason,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v4.16-rc4]
url:
https://github.com/0day-ci/linux/commits/Jason-Vas-Dias/x86-vdso-on-Intel-VDSO-should-handle-CLOCK_MONOTONIC_RAW/20180312-141707
config: i386-randconfig-x006-201810 (attached as .config)
co
On Mon, 12 Mar 2018 14:08:34 +1100, "Tobin C. Harding" said:
> removal patch that 768 was a lot of stack space. That comment did,
> however say 'deep in some transfer call chain'. I don't know what a
> 'transfer call chain' (the transfer bit) is but is there some heuristic
> we can use to know h
Audit link denied events generate duplicate PATH records which disagree
in different ways from symlink and hardlink denials.
audit_log_link_denied() should not directly generate PATH records.
While we're at it, remove the now useless struct path argument.
See: https://github.com/linux-audit/audit-
Audit link denied events for symlinks were missing the parent PATH
record. Add it. Since the full pathname may not be available,
reconstruct it from the path in the nameidata supplied.
See: https://github.com/linux-audit/audit-kernel/issues/21
Signed-off-by: Richard Guy Briggs
---
fs/namei.c
Audit link denied events for symlinks had duplicate PATH records rather
than just updating the existing PATH record. Update the symlink's PATH
record with the current dentry and inode information.
See: https://github.com/linux-audit/audit-kernel/issues/21
Signed-off-by: Richard Guy Briggs
---
f
On 03/09/2018 11:32 PM, Stephen Kitt wrote:
> In preparation to enabling -Wvla, remove VLAs and replace them with
> fixed-length arrays instead.
>
> scsi_dh_{alua,emc,rdac} use variable-length array declarations to
> store command blocks, with the appropriate size as determined by
> COMMAND_SIZE.
On Fri, Mar 09, 2018 at 04:21:37PM -0800, Daniel Lustig wrote:
> On 3/9/2018 2:57 PM, Palmer Dabbelt wrote:
> > On Fri, 09 Mar 2018 13:30:08 PST (-0800), parri.and...@gmail.com wrote:
> >> On Fri, Mar 09, 2018 at 10:54:27AM -0800, Palmer Dabbelt wrote:
> >>> On Fri, 09 Mar 2018 10:36:44 PST (-0800)
On Mon, Mar 12, 2018 at 06:58:04AM +0100, Stefan Wahren wrote:
> Hi Tobin,
>
> > "Tobin C. Harding" hat am 12. März 2018 um 06:46
> > geschrieben:
> >
> >
> > On Mon, Mar 12, 2018 at 12:37:53PM +1100, Tobin C. Harding wrote:
> > > The kernel would like to have all stack VLA usage removed[1].
Hi
> -Original Message-
> From: 李書帆 [mailto:leechu...@gmail.com]
> Sent: 2018年3月12日 13:22
> To: Jun Li
> Cc: Greg Kroah-Hartman ;
> heikki.kroge...@linux.intel.com; li...@roeck-us.net; g...@kroah.com;
> shufan_...@richtek.com; cy_hu...@richtek.com;
> linux-kernel@vger.kernel.org; linux-...
Hi Tobin,
> "Tobin C. Harding" hat am 12. März 2018 um 06:46 geschrieben:
>
>
> On Mon, Mar 12, 2018 at 12:37:53PM +1100, Tobin C. Harding wrote:
> > The kernel would like to have all stack VLA usage removed[1]. The array
> > here is fixed (declared with a const variable) but it appears like a
Hi Huacai,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.16-rc5 next-20180309]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits
On Monday 12 March 2018 01:05 AM, Richard Weinberger wrote:
Am Freitag, 9. März 2018, 11:50:47 CET schrieb Arvind Yadav:
if device_register() returned an error! Always use put_device()
to give up the reference initialized.
Arvind Yadav (2):
[PATCH 1/2] mtd: use put_device() if device_regis
On Mon, Mar 12, 2018 at 12:37:53PM +1100, Tobin C. Harding wrote:
> The kernel would like to have all stack VLA usage removed[1]. The array
> here is fixed (declared with a const variable) but it appears like a VLA
> to the compiler. Also, currently we are putting 768 bytes on the
> stack. This
Currently the VDSO does not handle
clock_gettime( CLOCK_MONOTONIC_RAW, &ts )
on Intel / AMD - it calls
vdso_fallback_gettime()
for this clock, which issues a syscall, having an unacceptably high
latency (minimum measurable time or time between measurements)
of 300-700ns on 2 2.
On Sun, Mar 11, 2018 at 03:55:41PM +0800, 焦晓冬 wrote:
> Peter pointed out in this patch https://patchwork.kernel.org/patch/9771921/
> that the spinning-lock used at __schedule() should be RCsc to ensure
> visibility of writes prior to __schedule when the task is to be migrated to
> another CPU.
>
>
Currently the VDSO does not handle
clock_gettime( CLOCK_MONOTONIC_RAW, &ts )
on Intel / AMD - it calls
vdso_fallback_gettime()
for this clock, which issues a syscall, having an unacceptably high
latency (minimum measurable time or time between measurements)
of 300-700ns on 2 2.
Hello, Rafael:
2018-03-05 16:47 GMT+08:00 Ganesh Mahendran :
> single_open() interface requires that the whole output must
> fit into a single buffer. This will lead to timeout when
> system memory is not in a good situation.
>
> This patch use seq_open() to show wakeup stats. This method
> need o
When a perf_event is attached to parent cgroup, it should count events
for all children cgroups:
parent_group < perf_event
\
- child_group < process(es)
However, in our tests, we found this perf_event cannot report reliable
results. This is because perf_event->cgrp and cpuctx->
Liebe Freunde
Ich habe ein Geschäft von $ 65.400.000.00 Million (fünfundsechzig Millionen,
vierhunderttausend US-Dollar), die er in unserer Bank hinterlegt hat und gerade
lügt, nicht beansprucht zu teilen, sollten Sie interessiert sein. Sollten Sie
interessiert sein, wenden Sie sich bitte an me
There are two parameters, ref_clk and coefficient, for U2 slew rate
calibrate which may vary on different SoCs, here allow them to be
configurable
Signed-off-by: Chunfeng Yun
---
drivers/phy/mediatek/phy-mtk-tphy.c | 20 +++-
1 file changed, 15 insertions(+), 5 deletions(-)
diff
Add two properties of ref_clk and coefficient used by U2 slew rate
calibrate which may vary on different SoCs
Signed-off-by: Chunfeng Yun
---
Documentation/devicetree/bindings/phy/phy-mtk-tphy.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/phy/phy-m
The default value of mcu_bus_ck_gate_en is 1, if clear it, will
prevent system to enter deep idle mode, so keep its default value
and without affecting PCIe function.
Signed-off-by: Chunfeng Yun
---
drivers/phy/mediatek/phy-mtk-tphy.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff
On Fri, Mar 09, 2018 at 12:17:07PM -0800, Paul E. McKenney wrote:
> On Fri, Mar 09, 2018 at 02:57:00PM +0800, Boqun Feng wrote:
> > On Thu, Mar 08, 2018 at 07:42:55AM -0800, Paul E. McKenney wrote:
> > > On Thu, Mar 08, 2018 at 04:30:06PM +0800, Boqun Feng wrote:
> > > > On Thu, Mar 08, 2018 at 12:
Hi Jun,
Thank you.
2018-03-12 12:33 GMT+08:00 Jun Li :
> Hi,
>
>> +static irqreturn_t _tcpci_irq(int irq, void *dev_id) {
>> + struct tcpci *tcpci = dev_id;
>> +
>> + return tcpci_irq(tcpci);
>> +}
>>
> ...
>
>> + err = devm_request_threaded_irq(&client->dev, client->irq, NULL,
>> +
On Sun, Mar 11, 2018 at 10:02:04PM -0700, Eric Biggers wrote:
> On Mon, Mar 12, 2018 at 03:49:40PM +1100, Tobin C. Harding wrote:
> > The kernel would like to have all stack VLA usage removed[1].
>
> Can you please stop writing this? The Linux kernel isn't sentient; it doesn't
> "like" anything.
On Mon, Mar 12, 2018 at 03:49:40PM +1100, Tobin C. Harding wrote:
> The kernel would like to have all stack VLA usage removed[1].
Can you please stop writing this? The Linux kernel isn't sentient; it doesn't
"like" anything. You need to explain why *you* (and other people) believe these
changes
Currently the VDSO does not handle
clock_gettime( CLOCK_MONOTONIC_RAW, &ts )
on Intel / AMD - it calls
vdso_fallback_gettime()
for this clock, which issues a syscall, having an unacceptably high
latency (minimum measurable time or time between measurements)
of 300-700ns on 2 2.
The kernel would like to have all stack VLA usage removed[1]. Here the
array is declared using a variable that is declared using a constant
statement but the compiler still emits a warning. We can clear the
warning bu using the constant statement directly. The buffer size
variable is set to zero
The kernel would like to have all stack VLA usage removed[1]. Here the
array is declared using a variable that is declared using a constant
statement but the compiler still emits a warning. We can clear the
warning bu using the constant statement directly. In place of later
usage of the size var
On Saturday 10 March 2018 05:29 PM, Linus Walleij wrote:
>
> But this patch doesn't hide the partition from userspace does it?
>
> They will still appear in /dev/mmcblk0boot1 etc.
>
> Just not reported as "real" partitions in /proc/partitions.
>
> Or do I misunderstand it?
>
>
You are correct. T
On Sun, Mar 11, 2018 at 01:09:31PM -0700, matthew.gerl...@linux.intel.com wrote:
>
>
> On Mon, 5 Mar 2018, Alan Tull wrote:
>
>
> Hi Hao,
>
> I do think we should consider different hw implementations with this code
> because it does look like most of it is generic. Specifically, I think
> we
On 09-02-18, 14:28, Viresh Kumar wrote:
> The "cooling-min-level" and "cooling-max-level" properties are not
> parsed by any part of kernel currently and the max cooling state of a
> CPU cooling device is found by referring to the cpufreq table instead.
>
> Remove the unused bindings.
>
> Signed-
On 09-02-18, 14:28, Viresh Kumar wrote:
> The "cooling-min-level" and "cooling-max-level" properties are not
> parsed by any part of the kernel currently and the max cooling state of
> gpio-fan cooling device is found by referring to the
> "gpio-fan,speed-map" instead.
>
> Remove the unused proper
Hi,
> +static irqreturn_t _tcpci_irq(int irq, void *dev_id) {
> + struct tcpci *tcpci = dev_id;
> +
> + return tcpci_irq(tcpci);
> +}
>
...
> + err = devm_request_threaded_irq(&client->dev, client->irq, NULL,
> + _tcpci_irq,
>
On 09-02-18, 10:03, Neil Armstrong wrote:
> On 09/02/2018 09:58, Viresh Kumar wrote:
> > The "cooling-min-level" and "cooling-max-level" properties are not
> > parsed by any part of the kernel currently and the max cooling state of
> > a CPU cooling device is found by referring to the cpufreq table
On 16-01-18, 15:22, Viresh Kumar wrote:
> This extends the sysfs interface for thermal cooling devices and exposes
> some pretty useful statistics. These statistics have proven to be quite
> useful specially while doing benchmarks related to the task scheduler,
> where we want to make sure that not
This patch exports the host capabilities to debugfs
This idea of sharing host capabilities over debugfs
came up from Abbas Raza
Earlier discussions:
https://lkml.org/lkml/2018/3/5/357
https://www.spinics.net/lists/linux-mmc/msg48219.html
Signed-off-by: Harish Jenny K N
---
Changes in v9
- More
The kernel would like to have all stack VLA usage removed[1]. This is a
test function so the execution speed is not critical. We can allocate
memory for this buffer instead of using a VLA. If kmalloc() fails just
return.
Allocate buffer with kmalloc().
[1]: https://lkml.org/lkml/2018/3/7/621
The A33-OLinuXino has a DC jack wired to the onboard PMIC's ACIN pins.
There is also a battery connector, wired to the PMIC's battery charger.
Enable the power supplies for both these components.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a33-olinuxino.dts | 8
1 file chan
None of the common regulators defined in sunxi-common-regulators.dtsi
are used for the A33-OLinuXino.
Drop the include.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a33-olinuxino.dts | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/boot/dts/sun8i-a33-olinuxino.dts
b/arch/
Hi,
Here are some cleanup and improvements for the A33-OLinuXino device
tree. The first two patches drop some unneeded bits. The latter two
enable peripherals that we now support.
ChenYu
Chen-Yu Tsai (4):
ARM: dts: sun8i: a33: Drop GPIO pinmux settings for A33-OLinuXino
ARM: dts: sun8i: a33:
Normal GPIO usage does not need an additional pinmix setting. Exclusive
usage of the pin will be guaranteed by the driver.
Drop the extra pinmux settings.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-a33-olinuxino.dts | 23 +--
1 file changed, 1 insertion(+), 22 d
The A33-OLinuXino routes the SoC's headphone output to a headphone jack,
and the microphone input to a microphone jack. Power to the microphone
is provided by MBIAS.
This patch enables the various parts of the codec, and adds widgets and
routes for simple-card.
HBIAS is connected to the microphon
The A23/A33 reference tablet design has a DC barrel tied to the ACIN
of the PMIC. And being a tablet, it has a Li-Po battery.
Enable both power supplies in the device tree.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sun8i-reference-design-tablet.dtsi | 8
1 file changed, 8 inser
On Sun, Mar 11, 2018 at 11:24:38PM +, Ian Armstrong wrote:
> On Sat, 10 Mar 2018 16:57:41 +
> "French, Nicholas A." wrote:
>
> > > > No what if the framebuffer driver is just requested as a
> > > > secondary step after firmware loading?
> > >
> > > Its a possibility. The decoder firmwar
On Thu, 08 Mar 2018 11:02:29 -0800
Alexander Duyck wrote:
> From: Alexander Duyck
>
> This patch is meant to add some basic functionality to support for SR-IOV
> on devices when the VFs are not managed by some other entity in the device
> other than the kernel.
>
> A new sysfs value called sri
Hi Will,
2018-03-01 16:16 GMT+09:00 Masahiro Yamada :
> 2018-02-27 0:04 GMT+09:00 Will Deacon :
>> Hi everyone,
>>
>> This is version two of the RFC I previously posted here:
>>
>> https://www.spinics.net/lists/arm-kernel/msg634719.html
>>
>> Changes since v1 include:
>>
>> * Fixed __clear_bi
This is the start of the stable review cycle for the 3.2.101 release.
There are 104 patches in this series, which will be posted as responses
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Wed Mar 14 12:00:00 UTC 2018.
Anything rece
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Andi Kleen
commit 527f6570300980251e818e80865b437eefb4e5d3 upstream.
gcc 4.8 warns
/backup/lsrc/git/linux-lto-2.6/drivers/net/wireless/ath/ath6kl/sdio.c:
In function 'ath6kl_sdio_enable_scatt
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Andi Kleen
commit af2c8ffe56133928355d1d51978b35115ffbbc2a upstream.
gcc 4.8 warns for this memcpy. While the copy size is correct, the whole
copy seems to be a nop because the destination is
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Han Shen
commit 7c8f0db0d024efda38976fc2acf7743f458e1d96 upstream.
GCC 4.8 is spitting out uninitialized-variable warnings against
"drivers/net/wireless/rtlwifi/rtl8192c/dm_common.c". This pa
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
I ran into a 4.9 build warning in randconfig testing, starting with the
KAISER patches:
arch/x86/kernel/ldt.c: In function 'alloc_ldt_struct':
arch/x86/include/asm/pgtable_types.
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Alexandre Oliva
commit 5addc0de28f5e286f9d121112c450807b5a5 upstream.
Alexandre Oliva says:
"It's an issue brought about by GCC 4.7's partial-inlining, that ends up
splitting the udelay
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Kuninori Morimoto
commit c2fa3edc58a262dfcb7aea78e24661e90e00098c upstream.
__usbhs_for_each_pipe() is the macro which moves around each pipe,
but it has a bug which didn't care about 1st pipe
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Larry Finger
commit 8925d518663628f769173d3586c66987fdd3ab61 upstream.
when this driver is built with "make W=1", the following warning is printed:
drivers/net/wireless/rtlwifi/rtl8192de/dm.c
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Frantisek Hrbata
commit 5f41ea0386a53414d688cfcaa321a78310e5f7c1 upstream.
The gcov in-memory format changed in gcc 4.7. The biggest change, which
requires this special implementation, is tha
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Larry Finger
commit f761b6947dde42890beea59b020e1be87491809e upstream.
With gcc 4.7.x, the following warning is issued as the routine that sets
the array has the possibility of not initializin
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Kuninori Morimoto
commit 925403f425a4a9c503f2fc295652647b1eb10d82 upstream.
Current usbhsx_for_each_xxx macro will read out-of-array's
memory after last loop operation.
It was not good C langu
Ah, sorry, I used a wrong Message-Id in In-reply-to, please ignore this one.
Sorry about that.
On 2018年03月12日 11:37, Shunqian Zheng wrote:
rk3399 have two ISP, but we havn't test isp1, so just add isp0 at present.
Signed-off-by: Shunqian Zheng
Signed-off-by: Jacob Chen
---
arch/arm64/boot
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Darren Kenny
commit af189c95a371b59f493dbe0f50c0a09724868881 upstream.
Fixes: 117cc7a908c83 ("x86/retpoline: Fill return stack buffer on vmexit")
Signed-off-by: Darren Kenny
Signed-off-by: Th
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Frantisek Hrbata
commit 8cbce376e3fdf4a21f59365aefbb52eac3c2e312 upstream.
Since also the gcov structures(gcov_info, gcov_fn_info, gcov_ctr_info) can
change between gcc releases, as shown in g
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Frantisek Hrbata
commit 17c568d60af5a810208baf116dc174a2005c6c3e upstream.
Compile the correct gcov implementation file for the specific gcc version.
Signed-off-by: Frantisek Hrbata
Cc: Jan
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Syam Sidhardhan
commit e10b9969f217c948c5523045f44eba4d3a758ff0 upstream.
In this API, we were using sizeof operator for an array
given as function argument, which is invalid.
However this API
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Han Shen
commit 6b13eb1baa17b8746f96bd536d2897ec86e823d9 upstream.
Fix warnings about unused local typedefs (reported by gcc 4.8).
Signed-off-by: Han Shen (shen...@google.com)
Change-Id: I4
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Tim Gardner
commit b5495b4217d3fa64deac479db83dbede149af7d8 upstream.
Dynamically allocate a couple of the larger stack variables in order to
reduce the stack footprint below 1024. gcc-4.8
se
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Masami Hiramatsu
commit c1804a236894ecc942da7dc6c5abe209e56cba93 upstream.
Mark __x86_indirect_thunk_* functions as blacklist for kprobes
because those functions can be called from anywhere in
Add hooks to enable/disable a per-CPU IRQ for VMbus. These hooks
are in the architecture independent setup and shutdown paths for
Hyper-V. They are being added as staging for upcoming code for
Linux guests on Hyper-V on ARM64. The x86/x64 implementation
is null because VMbus interrupts on x86/x64
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit e383095c7fe8d218e00ec0f83e4b95ed4e627b02 upstream.
If sysfs is disabled and RETPOLINE not defined:
arch/x86/kernel/cpu/bugs.c:97:13: warning: ‘spectre_v2_bad_module’ de
rk3399 have two ISP, but we havn't test isp1, so just add isp0 at present.
Signed-off-by: Shunqian Zheng
Signed-off-by: Jacob Chen
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
b/arc
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: David Woodhouse
commit 66f793099a636862a71c59d4a6ba91387b155e0c upstream.
There's no point in building init code with retpolines, since it runs before
any potentially hostile userspace does. A
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: "zhenwei.pi"
commit 98f0fceec7f84d80bc053e49e596088573086421 upstream.
In section <2. Runtime Cost>, fix wrong index.
Signed-off-by: zhenwei.pi
Signed-off-by: Thomas Gleixner
Cc: dave.han..
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Waiman Long
commit 1df37383a8aeabb9b418698f0bcdffea01f4b1b2 upstream.
It doesn't make sense to have an indirect call thunk with esp/rsp as
retpoline code won't work correctly with the stack po
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Andrey Ryabinin
commit 196bd485ee4f03ce4c690bfcf38138abfcd0a4bc upstream.
Currently we use current_stack_pointer() function to get the value
of the stack pointer register. Since commit:
f5c
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: David Woodhouse
commit 2961298efe1ea1b6fc0d7ee8b76018fa6c0bcef2 upstream.
We want to expose the hardware features simply in /proc/cpuinfo as "ibrs",
"ibpb" and "stibp". Since AMD has separate
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: KarimAllah Ahmed
commit 9005c6834c0ffdfe46afa76656bd9276cca864f6 upstream.
[dwmw2: Use ARRAY_SIZE]
Signed-off-by: KarimAllah Ahmed
Signed-off-by: David Woodhouse
Signed-off-by: Thomas Gleix
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit 66c117d7fa2ae429911e60d84bf31a90b2b96189 upstream.
Richard reported the following crash:
[0.036000] BUG: unable to handle kernel paging request at 55501e06
[0.0
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: David Woodhouse
commit 9ecccfaa7cb5249bd31bdceb93fcf5bedb8a24d8 upstream.
Fixes: 87590ce6e ("sysfs/cpu: Add vulnerability folder")
Signed-off-by: David Woodhouse
Signed-off-by: Thomas Gleixne
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: David Woodhouse
commit 76b043848fd22dbf7f8bf3a1452f8c70d557b860 upstream.
Enable the use of -mindirect-branch=thunk-extern in newer GCC, and provide
the corresponding thunks. Provide assembler
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Andi Kleen
commit caf7501a1b4ec964190f31f9c3f163de252273b8 upstream.
There's a risk that a kernel which has full retpoline mitigations becomes
vulnerable when a module gets loaded that hasn't
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Paul Gortmaker
commit 7b91747d42a1012e3781dd09fa638d113809e3fd upstream.
Most of these have been purged years ago. This one silently lived
on until commit 69349c2dc01c489eccaa4c472542c08e370c
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Williams
commit 304ec1b050310548db33063e567123fae8fd0301 upstream.
Quoting Linus:
I do think that it would be a good idea to very expressly document
the fact that it's not that th
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: David Woodhouse
commit 99c6fa2511d8a683e61468be91b83f85452115fa upstream.
Add the bug bits for spectre v1/2 and force them unconditionally for all
cpus.
Signed-off-by: David Woodhouse
Signed
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
commit 62a67e123e058a67db58bc6a14354dd037bafd0a upstream.
Should be easier when following boot paths. It probably is a left over
from the x86 unification eons ago.
No function
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
commit 69df353ff305805fc16082d0c5bfa6e20fa8b863 upstream.
Take a look at the first instruction byte before optimizing the NOP -
there might be something else there already, lik
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
commit f005f5d860e0231fe212cfda8c1a3148b99609f4 upstream.
asm/alternative.h isn't directly useful from assembly, but it
shouldn't break the build.
Signed-off-by: Andy Lutomirs
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 8fa80c503b484ddc1abbd10c7cb2ab81f3824a50 upstream.
For architectures providing their own implementation of
array_index_mask_nospec() in asm/barrier.h, attempting to use WARN
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Tom Lendacky
commit 694d99d40972f12e59a3696effee8a376b79d7c8 upstream.
AMD processors are not subject to the types of attacks that the kernel
page table isolation feature protects against. Th
3.2.101-rc1 review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
commit 65fc985b37dc241c4db7cd32adcbc989193fe3c8 upstream.
We add another 32-bit vector at the end of the ->x86_capability
bitvector which collects bugs present in CPUs. After a
1 - 100 of 517 matches
Mail list logo
