From: Peter Enderborg
This i preparation for switching to RCU locks. To be able to use
RCU we need atomic switched pointer. This adds the dynamic
memory copying to be a single pointer. It copy all the
data structures in to new ones. This is an overhead
for writing rules but the benifit is RCU.
S
From: Peter Enderborg
This patch switch to using RCU locks instead of rwlocks. This has
the big advantage that it does not has preempt disable.
Signed-off-by: Peter Enderborg
Reported-by: Björn Davidsson
---
security/selinux/ss/services.c | 162 +
1 fil
From: Peter Enderborg
To be able to use rcu locks we seed to address the policydb
though a pointer. This preparation removes the export of the
policydb and send pointers to it through parameter agruments.
Signed-off-by: Peter Enderborg
---
security/selinux/ss/mls.c | 69 --
From: Peter Enderborg
To be able to use rcu locks we seed to address the policydb
though a pointer. This patch adds a pointer structure to
repleace the static policydb.
Signed-off-by: Peter Enderborg
---
security/selinux/ss/services.c | 274 ++---
1 file cha
On 01/26/2018 08:41 AM, Geert Uytterhoeven wrote:
Hi Farhan,
On Thu, Jan 25, 2018 at 4:47 PM, Farhan Ali wrote:
This series of patches are in preparation for enabling an additional
tty and console for a S390 KVM guest using a virtio-gpu device[1].
One of the steps to do this would be to enab
After checking all possible call chains to drbd_resync_finished(),
my tool finds that this function is never called in atomic context,
namely never in an interrupt handler or holding a spinlock.
And it calls schedule_timeout_interruptible() before kmalloc(),
so it indicates that drbd_resync_finis
On Tue, Jan 23, 2018 at 12:28:08PM +, Suzuki K Poulose wrote:
> We enable hardware DBM bit in a capable CPU, very early in the
> boot via __cpu_setup. This doesn't give us a flexibility of
> optionally disable the feature, as the clearing the bit
> is a bit costly as the TLB can cache the setti
Hi Stephen, Al, Miklos,
I noticed that the vfs tree for-next branch is not yet in linux-next and
has a merge conflict with overlayfs-next branch, already in linux-next.
This is a trivial conflict due to the fact that commit f9c34674bc60 ("vfs:
factor out helpers d_instantiate_anon() and d_alloc_a
On Thu, Jan 25, 2018 at 11:38:04PM +0800, Icenowy Zheng wrote:
> >On Wed, Jan 24, 2018 at 09:10:34PM +0800, Icenowy Zheng wrote:
> >> 在 2018年1月22日星期一 CST 下午8:14:35,Maxime Ripard 写道:
> >> > On Sat, Jan 20, 2018 at 07:17:26AM +0800, Icenowy Zheng wrote:
> >> > > This is the RFC initial patchset for t
From: Colin Ian King
There are various assignments that are being made to variables that are
not read and the variables are being updated later on, hence the redundant
assignments can be removed.
Cleans up clang warnings:
drivers/staging/media/atomisp/i2c/ov5693/atomisp-ov5693.c:1950:8:
warning:
Patchset contains documentation of the sysfs interfaces for the
following five backlight drivers-
1) lp8788
2) lp855x
3) lm3639
4) adp5520
5) adp8860
It was compiled from data sheets, reading code and git history logs.
Aishwarya Pant (5):
backlight: lp8788: document sysfs attributes
backlight
On 01/26/2018 12:08 AM, Wang, Haiyue wrote:
On 2018-01-25 01:48, Corey Minyard wrote:
On 01/24/2018 10:06 AM, Haiyue Wang wrote:
The KCS (Keyboard Controller Style) interface is used to perform
in-band
IPMI communication between a server host and its BMC (BaseBoard
Management
Controllers).
On Fri, Jan 26, 2018 at 02:50:00PM +0100, Petr Oros wrote:
> But what in production? Edit boot params, restart server, grep /proc/cpuinfo
> and
> restart again? Why i can not read it just from dmesg?
Because you don't need the previous revision.
You only *happen* to need it now but that is being
Add documentation for sysfs interfaces of lp8788 backlight driver by
looking through the code and the git commit history.
Signed-off-by: Aishwarya Pant
---
Documentation/ABI/testing/sysfs-class-backlight-lp8788 | 10 ++
1 file changed, 10 insertions(+)
create mode 100644 Documentation/A
Add documentation for sysfs interface of Texas Instruments lp855x
backlight driver by reading code and looking through git commit logs.
Signed-off-by: Aishwarya Pant
---
.../ABI/testing/sysfs-class-backlight-lp855x | 19 +++
1 file changed, 19 insertions(+)
create mode
> -Original Message-
> From: Pali Rohár [mailto:pali.ro...@gmail.com]
> Sent: Thursday, January 25, 2018 5:06 PM
> To: Darren Hart
> Cc: Alexander Abrosimov ; Matthew Garrett
> ; Limonciello, Mario ; Andy
> Shevchenko ; platform-driver-...@vger.kernel.org; linux-
> ker...@vger.kernel.org
>
Add documentation for sysfs interfaces of Texas Instruments lm3639
backlight + flash led driver chip by looking through git commits and
reading code.
Signed-off-by: Aishwarya Pant
---
Documentation/ABI/testing/sysfs-class-backlight-lm3639 | 13 +
1 file changed, 13 insertions(+)
cre
Add documentation for sysfs interface of adp5520/adp5501 analog devices
backlight driver by reading code and looking through git commit logs.
Signed-off-by: Aishwarya Pant
---
.../ABI/testing/sysfs-class-backlight-adp5520 | 31 ++
1 file changed, 31 insertions(+)
create
Add documentation for sysfs interface of adp8860 series backlight
devices by reading through code and git commits.
Signed-off-by: Aishwarya Pant
---
.../ABI/testing/sysfs-class-backlight-adp8860 | 54 ++
1 file changed, 54 insertions(+)
create mode 100644 Documentation/
On Thu, Jan 25, 2018 at 05:50:18PM +0100, Giulio Benetti wrote:
> > > > > > On Sat, Jan 20, 2018 at 07:50:21PM +0100, Giulio Benetti wrote:
> > > > > > > On previous handling, if specified DRM_MODE_FLAG_N*SYNC,
> > > > > > > it was ignored,
> > > > > > > because only PHSYNC and PVSYNC were taken in
On Fri, Jan 26, 2018 at 11:29:15AM +0800, Wei Wang wrote:
> On 01/25/2018 09:41 PM, Michael S. Tsirkin wrote:
> > On Wed, Jan 24, 2018 at 06:42:41PM +0800, Wei Wang wrote:
> > > This patch adds support to walk through the free page blocks in the
> > > system and report them via a callback function.
> -Original Message-
> From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver-x86-
> ow...@vger.kernel.org] On Behalf Of Marco Martin
> Sent: Friday, January 26, 2018 5:21 AM
> To: linux-kernel@vger.kernel.org
> Cc: mj...@srcf.ucam.org; pali.ro...@gmail.com; dvh...@infradea
Commit-ID: caf7501a1b4ec964190f31f9c3f163de252273b8
Gitweb: https://git.kernel.org/tip/caf7501a1b4ec964190f31f9c3f163de252273b8
Author: Andi Kleen
AuthorDate: Thu, 25 Jan 2018 15:50:28 -0800
Committer: Thomas Gleixner
CommitDate: Fri, 26 Jan 2018 15:03:56 +0100
module/retpoline: Warn a
Commit-ID: 1e340c60d0dd3ae07b5bedc16a0469c14b9f3410
Gitweb: https://git.kernel.org/tip/1e340c60d0dd3ae07b5bedc16a0469c14b9f3410
Author: David Woodhouse
AuthorDate: Thu, 25 Jan 2018 16:14:12 +
Committer: Thomas Gleixner
CommitDate: Fri, 26 Jan 2018 15:53:17 +0100
x86/msr: Add defini
Commit-ID: 20ffa1caecca4db8f79fe665acdeaa5af815a24d
Gitweb: https://git.kernel.org/tip/20ffa1caecca4db8f79fe665acdeaa5af815a24d
Author: David Woodhouse
AuthorDate: Thu, 25 Jan 2018 16:14:15 +
Committer: Thomas Gleixner
CommitDate: Fri, 26 Jan 2018 15:53:18 +0100
x86/speculation: Ad
Commit-ID: a5b2966364538a0e68c9fa29bc0a3a1651799035
Gitweb: https://git.kernel.org/tip/a5b2966364538a0e68c9fa29bc0a3a1651799035
Author: David Woodhouse
AuthorDate: Thu, 25 Jan 2018 16:14:14 +
Committer: Thomas Gleixner
CommitDate: Fri, 26 Jan 2018 15:53:18 +0100
x86/cpufeature: Bla
Commit-ID: 5d10cbc91d9eb5537998b65608441b592eec65e7
Gitweb: https://git.kernel.org/tip/5d10cbc91d9eb5537998b65608441b592eec65e7
Author: David Woodhouse
AuthorDate: Thu, 25 Jan 2018 16:14:11 +
Committer: Thomas Gleixner
CommitDate: Fri, 26 Jan 2018 15:53:17 +0100
x86/cpufeatures: Ad
Hi Farhan,
On Fri, Jan 26, 2018 at 3:35 PM, Farhan Ali wrote:
> On 01/26/2018 08:41 AM, Geert Uytterhoeven wrote:
>> On Thu, Jan 25, 2018 at 4:47 PM, Farhan Ali
>> wrote:
>>> This series of patches are in preparation for enabling an additional
>>> tty and console for a S390 KVM guest using a vir
Hi, Andy,
On Thu, 2018-01-25 at 14:28 +0200, Andy Shevchenko wrote:
> On Thu, 2018-01-25 at 16:12 +0800, Zhang Rui wrote:
> >
> > The .prepare() callback of intel-lpss driver does nothing but wakes
> > up
> > its
> > children. I don't know if there is any reason to do so, but to me,
> > this is
>
From: Colin Ian King
Pointer dev is initialized and then re-assigned with the same value
a little later, hence the second assignment is redundant and can be
removed.
Cleans up clang warning:
drivers/usb/wusbcore/wa-nep.c:88:17: warning: Value stored to 'dev'
during its initialization is never re
Commit-ID: 5beda7d54eafece4c974cfa9fbb9f60fb18fd20a
Gitweb: https://git.kernel.org/tip/5beda7d54eafece4c974cfa9fbb9f60fb18fd20a
Author: Andy Lutomirski
AuthorDate: Thu, 25 Jan 2018 13:12:14 -0800
Committer: Thomas Gleixner
CommitDate: Fri, 26 Jan 2018 15:56:23 +0100
x86/mm/64: Fix vmap
Commit-ID: 36b3a7726886f24c4209852a58e64435bde3af98
Gitweb: https://git.kernel.org/tip/36b3a7726886f24c4209852a58e64435bde3af98
Author: Andy Lutomirski
AuthorDate: Thu, 25 Jan 2018 13:12:15 -0800
Committer: Thomas Gleixner
CommitDate: Fri, 26 Jan 2018 15:56:23 +0100
x86/mm/64: Tighten
Le 25/01/2018 à 14:17, Greg KH a écrit :
On Tue, Jan 23, 2018 at 12:31:47PM +0100, Frederic Barrat wrote:
ocxl.rst gives a quick, high-level view of opencapi.
Update ioctl-number.txt to reflect ioctl numbers being used by the
ocxl driver
Signed-off-by: Frederic Barrat
---
Documentation/AB
Commit-ID: 95ca0ee8636059ea2800dfbac9ecac6212d6b38f
Gitweb: https://git.kernel.org/tip/95ca0ee8636059ea2800dfbac9ecac6212d6b38f
Author: David Woodhouse
AuthorDate: Thu, 25 Jan 2018 16:14:09 +
Committer: Thomas Gleixner
CommitDate: Fri, 26 Jan 2018 15:53:16 +0100
x86/cpufeatures: Ad
Commit-ID: fc67dd70adb711a45d2ef34e12d1a8be75edde61
Gitweb: https://git.kernel.org/tip/fc67dd70adb711a45d2ef34e12d1a8be75edde61
Author: David Woodhouse
AuthorDate: Thu, 25 Jan 2018 16:14:10 +
Committer: Thomas Gleixner
CommitDate: Fri, 26 Jan 2018 15:53:16 +0100
x86/cpufeatures: Ad
There may be a race, when configuring two pwm channels, with different
prescaler values, when there's no active channel yet.
Add mutex lock to avoid concurrent access on pwm apply state.
This is also precursor patch for pwm capture support.
Signed-off-by: Fabrice Gasnier
---
drivers/pwm/pwm-stm3
On 26/01/18 01:03, kbuild test robot wrote:
> Fixes: 2935e3c38228 ("sfc: on 8000 series use TX queues for TX timestamps")
> Signed-off-by: Fengguang Wu
Acked-by: Edward Cree
Dave, can you take this directly or do you need it reposted without RFC tags?
I'm not sure what the procedure is for rob
Commit-ID: 0e6c16c652cadaffd25a6bb326ec10da5bcec6b4
Gitweb: https://git.kernel.org/tip/0e6c16c652cadaffd25a6bb326ec10da5bcec6b4
Author: Borislav Petkov
AuthorDate: Fri, 26 Jan 2018 13:11:36 +0100
Committer: Thomas Gleixner
CommitDate: Fri, 26 Jan 2018 15:53:19 +0100
x86/alternative: Pr
Add support for PMW input mode on pwm-stm32. STM32 timers support
period and duty cycle capture as long as they have at least two PWM
channels. One capture channel is used for period (rising-edge), one
for duty-cycle (falling-edge).
When there's only one channel available, only period can be captur
Currently, capture is based on timeout window to configure prescaler.
PWM capture framework provides 1s window at the time of writing.
There's place for improvement, after input signal has been captured once:
- Finer tune counter clock prescaler, by using 1st capture result (with
arbitrary margin)
dev is never assigned nor used. remove it.
Fixes: 7edf7369205b ("pwm: Add driver for STM32 plaftorm")
Signed-off-by: Fabrice Gasnier
---
drivers/pwm/pwm-stm32.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/pwm/pwm-stm32.c b/drivers/pwm/pwm-stm32.c
index 6139512..59524f9 100644
---
STM32 Timers can support up to 7 DMA requests:
- 4 channels, update, compare and trigger.
Optionally request part, or all DMAs from stm32-timers MFD core.
Also add routine to implement burst reads using DMA from timer registers.
This is exported. So, it can be used by child drivers, PWM capture
fo
Enable pwm3 input capture on stm32f429i-eval, by using DMA.
Signed-off-by: Fabrice Gasnier
---
arch/arm/boot/dts/stm32429i-eval.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/stm32429i-eval.dts
b/arch/arm/boot/dts/stm32429i-eval.dts
index 293ecb9..d5498dd 100644
--
Commit-ID: fec9434a12f38d3aeafeb75711b71d8a1fdef621
Gitweb: https://git.kernel.org/tip/fec9434a12f38d3aeafeb75711b71d8a1fdef621
Author: David Woodhouse
AuthorDate: Thu, 25 Jan 2018 16:14:13 +
Committer: Thomas Gleixner
CommitDate: Fri, 26 Jan 2018 15:53:18 +0100
x86/pti: Do not ena
The function long_sleep() calls mdelay() when in an interrupt handler.
But only charlcd_clear_display() and charlcd_init_display calls
long_sleep(), and my tool finds that the two functions
are never called in an interrupt handler.
Thus mdelay() and in_interrupt() are not necessary.
This is foun
I'm probably missing something obvious, but: Aren't phandles in practice
small consecutive integers assigned by dtc? If so, why not just have a
smallish static array mapping the small phandle values directly to
device node, instead of adding a pointer to every struct device_node? Or
one could de
Add support for DMAs to STM32 timers. STM32 Timers can support up to 7
dma requests: up to 4 channels, update, compare and trigger.
DMAs may be used to transfer data from pwm capture for instance.
DMA support is made optional, PWM capture support is also an option.
This is much more wise system-wid
Using input prescaler, capture unit will trigger DMA once every
configurable /2, /4 or /8 events (rising edge). This helps improve
period (only) capture accuracy at high rates.
Signed-off-by: Fabrice Gasnier
---
Changes in v2:
- Adopt DMA read from MFD core.
---
drivers/pwm/pwm-stm32.c
Commit-ID: 7a32fc51ca938e67974cbb9db31e1a43f98345a9
Gitweb: https://git.kernel.org/tip/7a32fc51ca938e67974cbb9db31e1a43f98345a9
Author: Borislav Petkov
AuthorDate: Fri, 26 Jan 2018 13:11:37 +0100
Committer: Thomas Gleixner
CommitDate: Fri, 26 Jan 2018 15:53:19 +0100
x86/nospec: Fix hea
This series adds support for capture to stm32-pwm driver.
Capture is based on DMAs.
- First two patches are precursor patches
- Subsequent two patches add support for requesting DMAs to MFD core
- Next three patches add support for capture to stm32-pwm driver
- This has been tested on stm32429i-eva
Commit-ID: 55fa19d3e51f33d9cd4056d25836d93abf9438db
Gitweb: https://git.kernel.org/tip/55fa19d3e51f33d9cd4056d25836d93abf9438db
Author: Borislav Petkov
AuthorDate: Fri, 26 Jan 2018 13:11:39 +0100
Committer: Thomas Gleixner
CommitDate: Fri, 26 Jan 2018 15:53:19 +0100
x86/bugs: Drop one
Allwinner H3 features a thermal sensor like the one in A33, but has its
register re-arranged, the clock divider moved to CCU (originally the
clock divider is in ADC) and added a pair of bus clock and reset.
Allwinner A83T features a thermal sensor similar to the H3, the ths clock,
the bus clock an
For adding newer sensor some basic rework of the code is necessary.
The SoCs after H3 has newer thermal sensor ADCs, which have two clock
inputs (bus clock and sampling clock) and a reset. The registers are
also re-arranged.
This commit reworks the code, adds the process of the clocks and
resets.
As we have gained the support for the thermal sensor in A83T,
we can now add its device nodes to the device tree.
The A83T seems to have a broken IRQ 31, thus we use here IRQ 41.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sun8i-a83t.dtsi | 8
1 file changed, 8 insertions(+)
d
As we have gained the support for the thermal sensor in H3 and H5,
we can now add its device nodes to the device tree. The H3 and H5 share
most of its compatible. The compatible and the thermal sensor cells
will be added in an additional patch per device.
Signed-off-by: Philipp Rossak
---
arch/a
This patch enables the the sid controller in the H3. It can be used
for thermal calibration data.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sun8i-h3.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi b/arch/arm/boot/dts/sun8i-h3.dtsi
index 3
This patch adds the thermal zones to the A83T. Sensor 0 is located in the
cpu cluster 0. Sensor 1 is located in cluster 1 and Sensor 3 is located
in the gpu.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sun8i-a83t.dtsi | 20
1 file changed, 20 insertions(+)
diff --gi
This patch adds the thermal zones to the H3. We have only one sensor and
that is placed in the cpu.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sun8i-h3.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi b/arch/arm/boot/dts/sun8i-h3.dtsi
ind
On Fri, Jan 26, 2018 at 1:22 AM, Chintan Pandya wrote:
> On 1/25/2018 8:20 PM, Rob Herring wrote:
>>
>> On Thu, Jan 25, 2018 at 4:14 AM, Chintan Pandya
>> wrote:
>>>
[...]
>> I'd guess that there's really only a few phandle lookups that occur
>> over and over.
>
> On my system, there are ~6.7k
This patch adds the missing compatible and the thermal sensor cells.
The H3 has one sensor.
Signed-off-by: Philipp Rossak
---
arch/arm/boot/dts/sun8i-h3.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi b/arch/arm/boot/dts/sun8i-h3.dtsi
index 8495deece
This patch adds support for the H3 ths sensor.
The H3 supports interrupts. The interrupt is configured to update the
the sensor values every second. The calibration data is writen at the
begin of the init process.
Signed-off-by: Philipp Rossak
---
drivers/iio/adc/sun4i-gpadc-iio.c | 29
This patch adds support for the A83T ths sensor.
The A83T does not support interrupts. This seems to be broken.
The calibration data is writen at the begin of the init process.
Signed-off-by: Philipp Rossak
---
drivers/iio/adc/sun4i-gpadc-iio.c | 38 ++
1 fil
This patch rewors the driver to support interrupts for the thermal part
of the sensor.
This is only available for the newer sensor (currently H3 and A83T).
The interrupt will be trigerd on data available and triggers the update
for the thermal sensors. All newer sensors have different amount of
se
Hi Arnd,
> The newly added btintel_download_firmware() dummy helper definition is
> incorrect, causing a build error when CONFIG_BT_INTEL is disabled:
>
> In file included from drivers/bluetooth/hci_ldisc.c:49:0:
> drivers/bluetooth/btintel.h:196:1: error: expected identifier or '(' before
> '{'
This patch reworks the driver to support nvmem calibration cells.
The driver checks if the nvmem calibration is supported and reads out
the nvmem. At the beginning of the startup process the calibration data
is written to the related registers.
Signed-off-by: Philipp Rossak
---
drivers/iio/adc/s
From: Icenowy Zheng
As the H3 SoC, which is also in sun8i line, has totally different
register map for the thermal sensor (a cut down version of GPADC), we
should rename A23/A33-specified registers to contain A33, in order to
prevent obfuscation with H3 registers. Currently these registers are
on
For adding newer sensor some basic rework of the code is necessary.
This commit reworks the code and allows the sampling start/end code and
the position of value readout register to be altered. Later the start/end
functions will be used to configure the ths and start/stop the
sampling.
Signed-off
For adding newer sensor some basic rework of the code is necessary.
This patch reworks the driver to be able to handle more than one
thermal sensor. Newer SoC like the A80 have 4 thermal sensors.
Because of this the maximal sensor count value was set to 4.
The sensor_id value is set during sensor
Allwiner H3 and A83T SoCs have a thermal sensor, which is a large refactored
version of the old Allwinner "GPADC" (although it have already only
thermal part left in A33).
This patch tried to add support for the sensor in H3 and A83T based on
the A33 thermal sensor driver by Quentin Schulz, which
This commit enables the SUN4I_GPADC config option and
sets the value to yes. This is needed to enable the ths sensors.
Signed-off-by: Philipp Rossak
---
arch/arm/configs/sunxi_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/sunxi_defconfig b/arch/arm/configs/sunxi_
The patch
regulator: empty the old suspend functions
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and s
The patch
regulator: add PM suspend and resume hooks
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and s
The patch
regulator: make regulator voltage be an array to support more states
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime i
The patch
regulator: leave one item to record whether regulator is enabled
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in th
After checking all possible call chains to mtip_hw_init() here,
my tool finds that this function is never called in atomic context,
namely never in an interrupt handler or holding a spinlock.
And mtip_hw_init() calls kzalloc_node(GFP_KERNEL) that can sleep,
so it indicates that mtip_hw_init() can c
The patch
regulator: added support for suspend states
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
On 01/26/2018 04:14 AM, Yves-Alexis Perez wrote:
> I know we'll still be able to manually enable PTI with a command line option,
> but it's also a hardening feature which has the nice side effect of emulating
> SMEP on CPU which don't support it (e.g the Atom boxes above).
For Meltdown-vulnerable
After checking all possible call chains to mtip_service_thread() here,
my tool finds that this function is never called in atomic context,
namely never in an interrupt handler or holding a spinlock.
And mtip_service_thread() calls wait_event_interruptible(),
so it indicates that mtip_hw_init() can
After checking all possible call chains to mtip_handle_tfe() here,
my tool finds that this function is never called in atomic context,
namely never in an interrupt handler or holding a spinlock.
And mtip_handle_tfe() is only called by mtip_service_thread() that
can sleep as described in the last p
On Fri, Jan 19, 2018 at 10:47 PM, Hans de Goede wrote:
> Stop the work on suspend, otherwise it may run between our suspend method
> running and the system suspending, possibly restarting the fan which
> we've just stopped.
>
> Note we already requeue the work on resume, so that we get a fresh spe
On 1/26/2018 7:27 AM, Dave Hansen wrote:
On 01/26/2018 04:14 AM, Yves-Alexis Perez wrote:
I know we'll still be able to manually enable PTI with a command line option,
but it's also a hardening feature which has the nice side effect of emulating
SMEP on CPU which don't support it (e.g the Atom b
On Tue, Jan 23, 2018 at 12:28:09PM +, Suzuki K Poulose wrote:
> Some variants of the Arm Cortex-55 cores (r0p0, r0p1, r1p0) suffer
> from an erratum 1024718, which causes incorrect updates when DBM/AP
> bits in a page table entry is modified without a break-before-make
> sequence. The work arou
On Fri, Jan 26, 2018 at 9:14 AM, Chintan Pandya wrote:
>
>> I'm probably missing something obvious, but: Aren't phandles in practice
>> small consecutive integers assigned by dtc? If so, why not just have a
>> smallish static array mapping the small phandle values directly to
>> device node, inste
We've noticed that fsgsbase_64 can fail intermittently with the
following error:
[RUN] ARCH_SET_GS(0x0) and clear gs, then schedule to 0x1
Before schedule, set selector to 0x1
other thread: ARCH_SET_GS(0x1) -- sel is 0x0
[FAIL] GS/BASE changed fro
After checking all possible call chains to on26_test_port() here,
my tool finds that this function is never called in atomic context,
namely never in an interrupt handler or holding a spinlock.
And on26_test_port() is only called by pi_probe_unit() that calls
wait_event() through pi_claim(),
so it
From: Colin Ian King
Pointer tv_nexus is being initialized a value and this is never read
and is later being updated with the same value. Remove the redundant
initialization so that the assignment to tv_nexus is performed later
and more local to when it is being read.
Cleans up clang warning:
dr
On Fri, 2018-01-26 at 14:35 +0800, Yu Chen wrote:
> On Thu, Jan 25, 2018 at 02:44:59PM -0800, Srinivas Pandruvada wrote:
> >
> > On Thu, 2018-01-25 at 19:08 +0800, Yu Chen wrote:
> >
> > Thanks for debugging.
> >
> > >
> > > The following warning was triggered after resumed from S3 -
> > > if a
On Thu, 2018-01-25 at 11:27 -0800, Davidlohr Bueso wrote:
> On Thu, 25 Jan 2018, Jason Gunthorpe wrote:
>
> > >
> > > Since the original post was referred to an ABBA deadlock, wouldn't we
> > > have to drop db_tab->mutex, then grab both in the proper order?
> >
> > I had understood that was only
On 26/01/18 12:25, Dave Martin wrote:
On Tue, Jan 23, 2018 at 12:28:03PM +, Suzuki K Poulose wrote:
KPTI capability is a security feature which should be enabled
when at least one CPU on the system needs it. Any late CPU
which needs the kernel support, should be prevented from
booting (and t
On 26/01/18 14:28, Marc Zyngier wrote:
Add the detection and runtime code for ARM_SMCCC_ARCH_WORKAROUND_1.
It is lovely. Really.
Signed-off-by: Marc Zyngier
---
arch/arm64/kernel/bpi.S| 20
arch/arm64/kernel/cpu_errata.c | 71 +-
After checking all possible call chains to btmrvl_send_sync_cmd(),
my tool finds that this function is never called in atomic context,
namely never in an interrupt handler or holding a spinlock.
And it calls wait_event_interruptible_timeout() after bt_skb_alloc(),
so it indicates that btmrvl_se
'spi_alloc_master()' calls should be balanced by a 'spi_master_put()' call.
'spi_controller_put()' is equivalent (see include/linux/spi/spi.h) but it
is cleaner and more logical to use 'spi_master_put()'.
Signed-off-by: Christophe JAILLET
---
drivers/spi/spi-sprd-adi.c | 2 +-
1 file changed, 1
Hi,
Il 26/01/2018 15:56, Maxime Ripard ha scritto:
On Thu, Jan 25, 2018 at 05:50:18PM +0100, Giulio Benetti wrote:
On Sat, Jan 20, 2018 at 07:50:21PM +0100, Giulio Benetti wrote:
On previous handling, if specified DRM_MODE_FLAG_N*SYNC,
it was ignored,
because only PHSYNC and PVSYNC were taken
From: Harini Katakam
Date: Fri, 26 Jan 2018 16:12:11 +0530
> From: Harini Katakam
>
> Handle HRESP error by doing a SW reset of RX and TX and
> re-initializing the descriptors, RX and TX queue pointers.
>
> Signed-off-by: Harini Katakam
> Signed-off-by: Michal Simek
> ---
> v2:
> Rebased on
On Fri, Jan 26, 2018 at 1:21 PM, Marco Martin wrote:
> Some laptops such as Dell Inspiron 7000 series have the
> tablet mode switch implemented in Intel ACPI,
> the events to enter and exit the tablet mode are 0xCC and 0xCD
Thanks for an update. It doesn't apply.
Please, rebase on top of our tes
On Fri, Jan 26, 2018 at 6:24 AM, Alan Cox wrote:
>> NetBSD (and the other BSD?) defines a structure for the arguments to
>> each syscall.
>
> Goes back to v7 or so but they put the syscall arguments into the uarea
> so that no pointers were needed (uarea being a per process mapping at a
> fixed ad
On 26/01/18 14:16, Dave Martin wrote:
On Tue, Jan 23, 2018 at 12:28:06PM +, Suzuki K Poulose wrote:
Add helpers for detecting an errata on list of midr ranges
of affected CPUs.
This doesn't describe what the patch does: instead, helpers are being
added for checking whether an MIDR falls in
From: Peng Li
Date: Fri, 26 Jan 2018 19:31:23 +0800
> This patch-set adds ethtool_ops.{get|set}_coalesce to VF and
> fix one related bug.
>
> HNS3 PF and VF driver use the common enet layer, as the
> ethtool_ops.{get|set}_coalesce to PF have upstreamed, just
> need add the ops to hns3vf_ethtool
On Fri, 26 Jan 2018, Henrique de Moraes Holschuh wrote:
On Thu, 25 Jan 2018, Rob Landley wrote:
That said, I don't think -h newcx should emit (or recognize) the
"TRAILER!!!1!" entry. That's kinda silly in-band signaling for 2018:
files have a length, pipes provide EOF, and each cpiox entry st
On Fri, Jan 26, 2018 at 3:20 PM, Baolin Wang wrote:
> On 26 January 2018 at 22:00, Daniel Thompson
> wrote:
>> On Fri, Jan 26, 2018 at 10:21:58AM +0100, Arnd Bergmann wrote:
>>> On Fri, Jan 26, 2018 at 4:03 AM, Baolin Wang wrote:
>>>
>>> Using ktime_get_seconds() avoids locking problems, but I
301 - 400 of 727 matches
Mail list logo