Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+21016130b0580a9de...@syzkaller.appspotmail.com
Tested on:
commit: 22dad84baabf apparmor: fix apparmor_secid_to_secctx incorr..
git tree:
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+21016130b0580a9de...@syzkaller.appspotmail.com
Tested on:
commit: 22dad84baabf apparmor: fix apparmor_secid_to_secctx incorr..
git tree:
On Sun, Sep 2, 2018 at 7:03 AM, syzbot
wrote:
>> On Sun, Sep 2, 2018 at 6:52 AM, John Johansen
>> wrote:
>>>
>>> On 09/01/2018 09:33 PM, Dmitry Vyukov wrote:
On Sat, Sep 1, 2018 at 11:18 AM, John Johansen
wrote:
>
> On 08/29/2018 07:17 PM, syzbot wrote:
>>
>>
On Sun, Sep 2, 2018 at 7:03 AM, syzbot
wrote:
>> On Sun, Sep 2, 2018 at 6:52 AM, John Johansen
>> wrote:
>>>
>>> On 09/01/2018 09:33 PM, Dmitry Vyukov wrote:
On Sat, Sep 1, 2018 at 11:18 AM, John Johansen
wrote:
>
> On 08/29/2018 07:17 PM, syzbot wrote:
>>
>>
Hi,
On Fri, Aug 24, 2018 at 3:42 AM, Dilip Kota wrote:
> From: Girish Mahadevan
>
> This driver supports GENI based SPI Controller in the Qualcomm SOCs. The
> Qualcomm Generic Interface (GENI) is a programmable module supporting a
> wide range of serial interfaces including SPI. This driver
Hi,
On Fri, Aug 24, 2018 at 3:42 AM, Dilip Kota wrote:
> From: Girish Mahadevan
>
> This driver supports GENI based SPI Controller in the Qualcomm SOCs. The
> Qualcomm Generic Interface (GENI) is a programmable module supporting a
> wide range of serial interfaces including SPI. This driver
On Sun, Sep 2, 2018 at 6:52 AM, John Johansen
wrote:
On 09/01/2018 09:33 PM, Dmitry Vyukov wrote:
On Sat, Sep 1, 2018 at 11:18 AM, John Johansen
wrote:
On 08/29/2018 07:17 PM, syzbot wrote:
Hello,
syzbot found the following crash on:
HEAD commit:817e60a7a2bb Merge branch
On Sun, Sep 2, 2018 at 6:52 AM, John Johansen
wrote:
> On 09/01/2018 09:33 PM, Dmitry Vyukov wrote:
>> On Sat, Sep 1, 2018 at 11:18 AM, John Johansen
>> wrote:
>>> On 08/29/2018 07:17 PM, syzbot wrote:
Hello,
syzbot found the following crash on:
HEAD commit:
On Sun, Sep 2, 2018 at 6:52 AM, John Johansen
wrote:
On 09/01/2018 09:33 PM, Dmitry Vyukov wrote:
On Sat, Sep 1, 2018 at 11:18 AM, John Johansen
wrote:
On 08/29/2018 07:17 PM, syzbot wrote:
Hello,
syzbot found the following crash on:
HEAD commit:817e60a7a2bb Merge branch
On Sun, Sep 2, 2018 at 6:52 AM, John Johansen
wrote:
> On 09/01/2018 09:33 PM, Dmitry Vyukov wrote:
>> On Sat, Sep 1, 2018 at 11:18 AM, John Johansen
>> wrote:
>>> On 08/29/2018 07:17 PM, syzbot wrote:
Hello,
syzbot found the following crash on:
HEAD commit:
On 09/01/2018 09:33 PM, Dmitry Vyukov wrote:
> On Sat, Sep 1, 2018 at 11:18 AM, John Johansen
> wrote:
>> On 08/29/2018 07:17 PM, syzbot wrote:
>>> Hello,
>>>
>>> syzbot found the following crash on:
>>>
>>> HEAD commit:817e60a7a2bb Merge branch 'nfp-add-NFP5000-support'
>>> git tree:
On 09/01/2018 09:33 PM, Dmitry Vyukov wrote:
> On Sat, Sep 1, 2018 at 11:18 AM, John Johansen
> wrote:
>> On 08/29/2018 07:17 PM, syzbot wrote:
>>> Hello,
>>>
>>> syzbot found the following crash on:
>>>
>>> HEAD commit:817e60a7a2bb Merge branch 'nfp-add-NFP5000-support'
>>> git tree:
On Sat, Sep 1, 2018 at 11:18 AM, John Johansen
wrote:
> On 08/29/2018 07:17 PM, syzbot wrote:
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:817e60a7a2bb Merge branch 'nfp-add-NFP5000-support'
>> git tree: net-next
>> console output:
On Sat, Sep 1, 2018 at 11:18 AM, John Johansen
wrote:
> On 08/29/2018 07:17 PM, syzbot wrote:
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:817e60a7a2bb Merge branch 'nfp-add-NFP5000-support'
>> git tree: net-next
>> console output:
On Sat, Sep 01, 2018 at 06:45:31PM -0400, Steven Rostedt wrote:
> On Sat, 1 Sep 2018 10:54:42 -0700
> "Paul E. McKenney" wrote:
>
> > On Sat, Sep 01, 2018 at 07:35:59PM +0200, Borislav Petkov wrote:
> > > This is a huge splat! It haz some perf* and sched* in it, I guess for
> > > peterz to stare
On Sat, Sep 01, 2018 at 06:45:31PM -0400, Steven Rostedt wrote:
> On Sat, 1 Sep 2018 10:54:42 -0700
> "Paul E. McKenney" wrote:
>
> > On Sat, Sep 01, 2018 at 07:35:59PM +0200, Borislav Petkov wrote:
> > > This is a huge splat! It haz some perf* and sched* in it, I guess for
> > > peterz to stare
From: Randy Dunlap
Fix the section mismatch warning in arch/x86/mm/pti.c:
WARNING: vmlinux.o(.text+0x6972a): Section mismatch in reference from the
function pti_clone_pgtable() to the function
.init.text:pti_user_pagetable_walk_pte()
The function pti_clone_pgtable() references
the function
From: Randy Dunlap
Fix the section mismatch warning in arch/x86/mm/pti.c:
WARNING: vmlinux.o(.text+0x6972a): Section mismatch in reference from the
function pti_clone_pgtable() to the function
.init.text:pti_user_pagetable_walk_pte()
The function pti_clone_pgtable() references
the function
The driver may sleep with holding a spinlock and in an interupt handler.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] usleep_range
drivers/pci/dwc/pcie-designware.c, 181:
usleep_range in dw_pcie_prog_outbound_atu
drivers/pci/dwc/pcie-designware-host.c, 479:
The driver may sleep with holding a spinlock and in an interupt handler.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] usleep_range
drivers/pci/dwc/pcie-designware.c, 181:
usleep_range in dw_pcie_prog_outbound_atu
drivers/pci/dwc/pcie-designware-host.c, 479:
On Thu, Aug 30, 2018 at 9:23 AM, Ard Biesheuvel
wrote:
> On 30 August 2018 at 17:06, Olof Johansson wrote:
>> On Wed, Aug 29, 2018 at 10:54 PM, Ard Biesheuvel
>> wrote:
>>> On 29 August 2018 at 20:59, Scott Branden
>>> wrote:
Hi Olof,
On 18-08-29 11:44 AM, Olof Johansson
On Thu, Aug 30, 2018 at 9:23 AM, Ard Biesheuvel
wrote:
> On 30 August 2018 at 17:06, Olof Johansson wrote:
>> On Wed, Aug 29, 2018 at 10:54 PM, Ard Biesheuvel
>> wrote:
>>> On 29 August 2018 at 20:59, Scott Branden
>>> wrote:
Hi Olof,
On 18-08-29 11:44 AM, Olof Johansson
Hi Linus,
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-fixes
for you to fetch changes up to
Hi Linus,
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-fixes
for you to fetch changes up to
This will be similar to /sys/kernel/mm/page_idle/bitmap documented in
Documentation/admin-guide/mm/idle_page_tracking.rst, however indexed
by process virtual address.
When using the global PFN indexed idle bitmap, we find 2 kind of
overheads:
- to track a task's working set, Brendan Gregg end up
This will be similar to /sys/kernel/mm/page_idle/bitmap documented in
Documentation/admin-guide/mm/idle_page_tracking.rst, however indexed
by process virtual address.
When using the global PFN indexed idle bitmap, we find 2 kind of
overheads:
- to track a task's working set, Brendan Gregg end up
For virtual machines, "accessed" bits will be set in guest page tables
and EPT/NPT. So for qemu-kvm process, convert HVA to GFN to GPA, then do
EPT/NPT walks. Thanks to the in-memslot linear HVA-GPA mapping, the conversion
can be done efficiently, outside of the loops for page table walks.
In
Signed-off-by: Fengguang Wu
---
arch/x86/kvm/Kconfig | 11 +++
arch/x86/kvm/Makefile | 4
2 files changed, 15 insertions(+)
diff --git a/arch/x86/kvm/Kconfig b/arch/x86/kvm/Kconfig
index 1bbec387d289..4c6dec47fac6 100644
--- a/arch/x86/kvm/Kconfig
+++ b/arch/x86/kvm/Kconfig
@@
This new /proc/PID/idle_bitmap interface aims to complement the current global
/sys/kernel/mm/page_idle/bitmap. To enable efficient user space driven
migrations.
The pros and cons will be discussed in changelog of "[PATCH] proc: introduce
/proc/PID/idle_bitmap". The driving force is to improve
The added pointer will be used by the /proc/PID/idle_bitmap code to
quickly identify QEMU task and walk EPT/NPT accordingly. For virtual
machines, the A bits will be set in guest page tables and EPT/NPT,
rather than the QEMU task page table.
This costs 8 bytes in task_struct which could be
For virtual machines, "accessed" bits will be set in guest page tables
and EPT/NPT. So for qemu-kvm process, convert HVA to GFN to GPA, then do
EPT/NPT walks. Thanks to the in-memslot linear HVA-GPA mapping, the conversion
can be done efficiently, outside of the loops for page table walks.
In
Signed-off-by: Fengguang Wu
---
arch/x86/kvm/Kconfig | 11 +++
arch/x86/kvm/Makefile | 4
2 files changed, 15 insertions(+)
diff --git a/arch/x86/kvm/Kconfig b/arch/x86/kvm/Kconfig
index 1bbec387d289..4c6dec47fac6 100644
--- a/arch/x86/kvm/Kconfig
+++ b/arch/x86/kvm/Kconfig
@@
This new /proc/PID/idle_bitmap interface aims to complement the current global
/sys/kernel/mm/page_idle/bitmap. To enable efficient user space driven
migrations.
The pros and cons will be discussed in changelog of "[PATCH] proc: introduce
/proc/PID/idle_bitmap". The driving force is to improve
The added pointer will be used by the /proc/PID/idle_bitmap code to
quickly identify QEMU task and walk EPT/NPT accordingly. For virtual
machines, the A bits will be set in guest page tables and EPT/NPT,
rather than the QEMU task page table.
This costs 8 bytes in task_struct which could be
This borrows host page table walk macros/functions to do EPT walk.
So it depends on them using the same level.
Dave Hansen raised the concern that hottest pages may be cached in TLB and
don't frequently set the accessed bits. The solution would be to invalidate TLB
for the mm being walked, when
This borrows host page table walk macros/functions to do EPT walk.
So it depends on them using the same level.
Dave Hansen raised the concern that hottest pages may be cached in TLB and
don't frequently set the accessed bits. The solution would be to invalidate TLB
for the mm being walked, when
Fixes: 5890bab41187 ("spi: at91-usart: add driver for at91-usart as spi")
Signed-off-by: kbuild test robot
---
spi-at91-usart.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/spi/spi-at91-usart.c b/drivers/spi/spi-at91-usart.c
index
Fixes: 5890bab41187 ("spi: at91-usart: add driver for at91-usart as spi")
Signed-off-by: kbuild test robot
---
spi-at91-usart.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/spi/spi-at91-usart.c b/drivers/spi/spi-at91-usart.c
index
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 420f51f4ab6bce6e580390729fadb89c31123636
commit: 269777aa530f3438ec1781586cdac0b5fe47b061 cpu/hotplug: Non-SMP machines
do not make use of booted_once
date: 3 weeks ago
config: i386-randconfig-b0-09011544
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 420f51f4ab6bce6e580390729fadb89c31123636
commit: 269777aa530f3438ec1781586cdac0b5fe47b061 cpu/hotplug: Non-SMP machines
do not make use of booted_once
date: 3 weeks ago
config: i386-randconfig-b0-09011544
/0day-ci/linux/commits/Radu-Pirea/Driver-for-at91-usart-in-spi-mode/20180901-165150
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings
/0day-ci/linux/commits/Radu-Pirea/Driver-for-at91-usart-in-spi-mode/20180901-165150
base: https://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git for-mfd-next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings
There is a sequence with non-ACPI root ports where the AER driver can
enable error reporting on the tree before port drivers have bound to
ports on the tree. The port driver assumes the AER driver will set up
error reporting afterwards, so instead add a check if error reporting
was set up first.
There is a sequence with non-ACPI root ports where the AER driver can
enable error reporting on the tree before port drivers have bound to
ports on the tree. The port driver assumes the AER driver will set up
error reporting afterwards, so instead add a check if error reporting
was set up first.
/linux/commits/Phil-Edworthy/clk-Add-functions-to-get-optional-clocks/20180901-154009
base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
WARNING: convert(1) not found, for SVG to PDF conversion i
/linux/commits/Phil-Edworthy/clk-Add-functions-to-get-optional-clocks/20180901-154009
base: https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
reproduce: make htmldocs
All warnings (new ones prefixed by >>):
WARNING: convert(1) not found, for SVG to PDF conversion i
On Sat, 1 Sep 2018 10:54:42 -0700
"Paul E. McKenney" wrote:
> On Sat, Sep 01, 2018 at 07:35:59PM +0200, Borislav Petkov wrote:
> > This is a huge splat! It haz some perf* and sched* in it, I guess for
> > peterz to stare at. And lemme add Paul for good measure too :)
> >
> > Kernel is -rc1 + 3
On Sat, 1 Sep 2018 10:54:42 -0700
"Paul E. McKenney" wrote:
> On Sat, Sep 01, 2018 at 07:35:59PM +0200, Borislav Petkov wrote:
> > This is a huge splat! It haz some perf* and sched* in it, I guess for
> > peterz to stare at. And lemme add Paul for good measure too :)
> >
> > Kernel is -rc1 + 3
Add the SMP2P nodes for the remoteproc states for adsp, cdsp and slpi.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 88
1 file changed, 88 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
Add the SMP2P nodes for the remoteproc states for adsp, cdsp and slpi.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 88
1 file changed, 88 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
From: Sibi Sankar
This patch adds the node to support AOSS reset driver on
SDM845
Signed-off-by: Sibi Sankar
[bjorn: Updated addresses to match the binding that was merged]
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 7 +++
1 file changed, 7 insertions(+)
From: Sibi Sankar
This patch adds the node to support AOSS reset driver on
SDM845
Signed-off-by: Sibi Sankar
[bjorn: Updated addresses to match the binding that was merged]
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 7 +++
1 file changed, 7 insertions(+)
Add regulator definitions for pm8998 and pmi8998 regulators on the MTP.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 216
1 file changed, 216 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845-mtp.dts
Add regulator definitions for pm8998 and pmi8998 regulators on the MTP.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 216
1 file changed, 216 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845-mtp.dts
On Sat, 1 Sep 2018, Al Viro wrote:
> IMO that's crap. In absolute majority of cases there is a guaranteed gap
> between the end of accessed object and the next page boundary.
So if that's the case, you're absolutely right. But I am unable to find
any such guarantee in our current code
On Sat, 1 Sep 2018, Al Viro wrote:
> IMO that's crap. In absolute majority of cases there is a guaranteed gap
> between the end of accessed object and the next page boundary.
So if that's the case, you're absolutely right. But I am unable to find
any such guarantee in our current code
On Fri, Aug 31, 2018 at 01:30:01PM -0700, Greg Hackmann wrote:
> On 08/31/2018 01:27 PM, Greg Hackmann wrote:
> > Change-Id: Ia0542dd8134e81cd5e1412e126545303c766f738
>
> Sorry, please disregard the Change-Id line. This is what I get for
> forgetting to re-run checkpatch after amending my commit
On Fri, Aug 31, 2018 at 01:30:01PM -0700, Greg Hackmann wrote:
> On 08/31/2018 01:27 PM, Greg Hackmann wrote:
> > Change-Id: Ia0542dd8134e81cd5e1412e126545303c766f738
>
> Sorry, please disregard the Change-Id line. This is what I get for
> forgetting to re-run checkpatch after amending my commit
On Fri, Aug 31, 2018 at 12:45 AM Julian Stecklina wrote:
>
> I've been spending some cycles on the XPFO patch set this week. For the
> patch set as it was posted for v4.13, the performance overhead of
> compiling a Linux kernel is ~40% on x86_64[1]. The overhead comes almost
> completely from TLB
On Fri, Aug 31, 2018 at 12:45 AM Julian Stecklina wrote:
>
> I've been spending some cycles on the XPFO patch set this week. For the
> patch set as it was posted for v4.13, the performance overhead of
> compiling a Linux kernel is ~40% on x86_64[1]. The overhead comes almost
> completely from TLB
Hi Jerome,
On Fri, Aug 31, 2018 at 12:02 PM, Jerome Brunet wrote:
> There are 7 digital mics on the MIC daughter board attached
> to the s400 board, so add the digital microphone codec to
> its DTS
>
> Signed-off-by: Jerome Brunet
> ---
> arch/arm64/boot/dts/amlogic/meson-axg-s400.dts | 9
Hi Jerome,
On Fri, Aug 31, 2018 at 12:02 PM, Jerome Brunet wrote:
> There are 7 digital mics on the MIC daughter board attached
> to the s400 board, so add the digital microphone codec to
> its DTS
>
> Signed-off-by: Jerome Brunet
> ---
> arch/arm64/boot/dts/amlogic/meson-axg-s400.dts | 9
Commit-ID: e78e5a91456fcecaa2efbb3706572fe043766f4d
Gitweb: https://git.kernel.org/tip/e78e5a91456fcecaa2efbb3706572fe043766f4d
Author: Samuel Neves
AuthorDate: Sat, 1 Sep 2018 21:14:52 +0100
Committer: Thomas Gleixner
CommitDate: Sat, 1 Sep 2018 23:01:56 +0200
x86/vdso: Fix lsl
Commit-ID: e78e5a91456fcecaa2efbb3706572fe043766f4d
Gitweb: https://git.kernel.org/tip/e78e5a91456fcecaa2efbb3706572fe043766f4d
Author: Samuel Neves
AuthorDate: Sat, 1 Sep 2018 21:14:52 +0100
Committer: Thomas Gleixner
CommitDate: Sat, 1 Sep 2018 23:01:56 +0200
x86/vdso: Fix lsl
On Sat, Sep 1, 2018 at 1:14 PM, Samuel Neves wrote:
> In the __getcpu function, lsl was using the wrong target
> and destination registers. Luckily, the compiler tends to
> choose %eax for both variables, so it has been working
> so far.
>
> Cc: x...@kernel.org
> Cc: sta...@vger.kernel.org
>
On Sat, Sep 1, 2018 at 1:14 PM, Samuel Neves wrote:
> In the __getcpu function, lsl was using the wrong target
> and destination registers. Luckily, the compiler tends to
> choose %eax for both variables, so it has been working
> so far.
>
> Cc: x...@kernel.org
> Cc: sta...@vger.kernel.org
>
In the __getcpu function, lsl was using the wrong target
and destination registers. Luckily, the compiler tends to
choose %eax for both variables, so it has been working
so far.
Cc: x...@kernel.org
Cc: sta...@vger.kernel.org
Signed-off-by: Samuel Neves
---
arch/x86/include/asm/vgtod.h | 2 +-
1
In the __getcpu function, lsl was using the wrong target
and destination registers. Luckily, the compiler tends to
choose %eax for both variables, so it has been working
so far.
Cc: x...@kernel.org
Cc: sta...@vger.kernel.org
Signed-off-by: Samuel Neves
---
arch/x86/include/asm/vgtod.h | 2 +-
1
Drop boilerplate license text and use SPDX identifier instead.
Signed-off-by: Tomasz Duszynski
---
drivers/iio/pressure/ms5611.h | 5 +
drivers/iio/pressure/ms5611_core.c | 5 +
drivers/iio/pressure/ms5611_i2c.c | 5 +
drivers/iio/pressure/ms5611_spi.c | 5 +
4 files
Drop boilerplate license text and use SPDX identifier instead.
Signed-off-by: Tomasz Duszynski
---
drivers/iio/pressure/ms5611.h | 5 +
drivers/iio/pressure/ms5611_core.c | 5 +
drivers/iio/pressure/ms5611_i2c.c | 5 +
drivers/iio/pressure/ms5611_spi.c | 5 +
4 files
Drop boilerplate license text and use SPDX identifier instead.
Signed-off-by: Tomasz Duszynski
---
drivers/iio/light/bh1750.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/iio/light/bh1750.c b/drivers/iio/light/bh1750.c
index a814828e69f5..493ca7420602 100644
Drop boilerplate license text and use SPDX identifier instead.
Signed-off-by: Tomasz Duszynski
---
drivers/iio/light/bh1750.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/iio/light/bh1750.c b/drivers/iio/light/bh1750.c
index a814828e69f5..493ca7420602 100644
Hi Greg,
On Sat, Sep 1, 2018 at 8:39 PM, Greg KH wrote:
> On Sat, Sep 01, 2018 at 03:38:13PM +0200, Miguel Ojeda wrote:
>> Hi Nick,
>>
>> On Sat, Sep 1, 2018 at 1:07 AM, Nick Desaulniers
>> wrote:
>> > Overall, pretty happy with this patch. Still some thoughts for a v3,
>> >> -#define
Hi Greg,
On Sat, Sep 1, 2018 at 8:39 PM, Greg KH wrote:
> On Sat, Sep 01, 2018 at 03:38:13PM +0200, Miguel Ojeda wrote:
>> Hi Nick,
>>
>> On Sat, Sep 1, 2018 at 1:07 AM, Nick Desaulniers
>> wrote:
>> > Overall, pretty happy with this patch. Still some thoughts for a v3,
>> >> -#define
On Sat, Sep 01, 2018 at 03:38:13PM +0200, Miguel Ojeda wrote:
> Hi Nick,
>
> On Sat, Sep 1, 2018 at 1:07 AM, Nick Desaulniers
> wrote:
> > Overall, pretty happy with this patch. Still some thoughts for a v3,
> >> -#define __visible __attribute__((externally_visible))
> >> diff --git
On Sat, Sep 01, 2018 at 03:38:13PM +0200, Miguel Ojeda wrote:
> Hi Nick,
>
> On Sat, Sep 1, 2018 at 1:07 AM, Nick Desaulniers
> wrote:
> > Overall, pretty happy with this patch. Still some thoughts for a v3,
> >> -#define __visible __attribute__((externally_visible))
> >> diff --git
[ Adding a few new people the the cc.
The issue is the worry about software-speculative accesses (ie
things like CONFIG_DCACHE_WORD_ACCESS - not talking about the hw
speculation now) accessing past RAM into possibly contiguous IO ]
On Sat, Sep 1, 2018 at 10:27 AM Linus Torvalds
wrote:
>
> If
[ Adding a few new people the the cc.
The issue is the worry about software-speculative accesses (ie
things like CONFIG_DCACHE_WORD_ACCESS - not talking about the hw
speculation now) accessing past RAM into possibly contiguous IO ]
On Sat, Sep 1, 2018 at 10:27 AM Linus Torvalds
wrote:
>
> If
For some number of systems with lpss_quirks enabled, on boot the system
goes through an acpi_lpss_resume() without a corresponding
acpi_lpss_suspend() having been called. In that case, it requires the
IOSF write to LPSS_IOSF_UNIT_LPIOEP / LPSS_IOSF_GPIODEF0 in order to
continue booting
For some number of systems with lpss_quirks enabled, on boot the system
goes through an acpi_lpss_resume() without a corresponding
acpi_lpss_suspend() having been called. In that case, it requires the
IOSF write to LPSS_IOSF_UNIT_LPIOEP / LPSS_IOSF_GPIODEF0 in order to
continue booting
On Sat, Sep 01, 2018 at 07:35:59PM +0200, Borislav Petkov wrote:
> This is a huge splat! It haz some perf* and sched* in it, I guess for
> peterz to stare at. And lemme add Paul for good measure too :)
>
> Kernel is -rc1 + 3 microcode loader patches ontop which should not be
> related.
It really
On Sat, Sep 01, 2018 at 07:35:59PM +0200, Borislav Petkov wrote:
> This is a huge splat! It haz some perf* and sched* in it, I guess for
> peterz to stare at. And lemme add Paul for good measure too :)
>
> Kernel is -rc1 + 3 microcode loader patches ontop which should not be
> related.
It really
Hi Arnd,
On Fri, Apr 13, 2018 at 11:50:12AM +0200, Arnd Bergmann wrote:
> We have four generations of stat() syscalls:
> - the oldstat syscalls that are only used on the older architectures
> - the newstat family that is used on all 64-bit architectures but
> lacked support for large files on
Hi Arnd,
On Fri, Apr 13, 2018 at 11:50:12AM +0200, Arnd Bergmann wrote:
> We have four generations of stat() syscalls:
> - the oldstat syscalls that are only used on the older architectures
> - the newstat family that is used on all 64-bit architectures but
> lacked support for large files on
On Sat, Sep 1, 2018 at 2:33 AM, Florian Weimer wrote:
> On 09/01/2018 05:39 AM, Andy Lutomirski wrote:
>>
>> Florian, do you think
>> glibc would be willing to add some magic to turn
>> clock_gettime(CLOCK_MONOTONIC, t) into
>> __vdso_clock_gettime_monotonic(t) when CLOCK_MONOTONIC is a constant?
On Sat, Sep 1, 2018 at 2:33 AM, Florian Weimer wrote:
> On 09/01/2018 05:39 AM, Andy Lutomirski wrote:
>>
>> Florian, do you think
>> glibc would be willing to add some magic to turn
>> clock_gettime(CLOCK_MONOTONIC, t) into
>> __vdso_clock_gettime_monotonic(t) when CLOCK_MONOTONIC is a constant?
This is a huge splat! It haz some perf* and sched* in it, I guess for
peterz to stare at. And lemme add Paul for good measure too :)
Kernel is -rc1 + 3 microcode loader patches ontop which should not be
related.
Thx.
---
[ 62.409125] =
[ 62.409129] WARNING:
This is a huge splat! It haz some perf* and sched* in it, I guess for
peterz to stare at. And lemme add Paul for good measure too :)
Kernel is -rc1 + 3 microcode loader patches ontop which should not be
related.
Thx.
---
[ 62.409125] =
[ 62.409129] WARNING:
On Sat, Sep 1, 2018 at 9:33 AM, Linus Torvalds
wrote:
> On Fri, Aug 31, 2018 at 3:21 PM Andy Lutomirski wrote:
>>
>> #ifdef CONFIG_X86_64
>> # define cpu_current_top_of_stack (cpu_tss_rw + TSS_sp1)
>> +# define rsp_scratch (cpu_tss_rw + TSS_sp2)
>> #endif
>
> Ugh. The above gets used by
On Sat, Sep 1, 2018 at 9:33 AM, Linus Torvalds
wrote:
> On Fri, Aug 31, 2018 at 3:21 PM Andy Lutomirski wrote:
>>
>> #ifdef CONFIG_X86_64
>> # define cpu_current_top_of_stack (cpu_tss_rw + TSS_sp1)
>> +# define rsp_scratch (cpu_tss_rw + TSS_sp2)
>> #endif
>
> Ugh. The above gets used by
On Fri, Aug 31, 2018 at 2:18 PM Jiri Kosina wrote:
>
> If noone has any clever idea how to work this around (I don't), I am
> afraid we'd have to ditch the whole DCACHE_WORD_ACCESS optimization, as
> it's silently dangerous.
No way in hell will I apply such a stupid patch.
It is NOT dangerous.
On Fri, Aug 31, 2018 at 2:18 PM Jiri Kosina wrote:
>
> If noone has any clever idea how to work this around (I don't), I am
> afraid we'd have to ditch the whole DCACHE_WORD_ACCESS optimization, as
> it's silently dangerous.
No way in hell will I apply such a stupid patch.
It is NOT dangerous.
On Sat, Sep 01, 2018 at 12:47:48PM +0200, Juergen Gross wrote:
> On 31/08/18 23:18, Jiri Kosina wrote:
> > On Wed, 29 Aug 2018, Juergen Gross wrote:
> >
> >> While being very unlikely I still believe this is possible. Any
> >> thoughts?
> >
> > So in theory we should somehow test whether the
On Sat, Sep 01, 2018 at 12:47:48PM +0200, Juergen Gross wrote:
> On 31/08/18 23:18, Jiri Kosina wrote:
> > On Wed, 29 Aug 2018, Juergen Gross wrote:
> >
> >> While being very unlikely I still believe this is possible. Any
> >> thoughts?
> >
> > So in theory we should somehow test whether the
Hi again,
Here is a short summary of what is missing in the microcode containers [1] [2].
I only included AMD family 15h and 17h.
Similar could be done for Intel CPUs.
I do believe having a latest microcode is a vital for the userspace security
because it provides
IBPB barrier.
Family 15h
Hi again,
Here is a short summary of what is missing in the microcode containers [1] [2].
I only included AMD family 15h and 17h.
Similar could be done for Intel CPUs.
I do believe having a latest microcode is a vital for the userspace security
because it provides
IBPB barrier.
Family 15h
On Fri, Aug 31, 2018 at 05:06:30PM +0100, Will Deacon wrote:
> Hi Paul,
>
> On Wed, Aug 29, 2018 at 02:10:53PM -0700, Paul E. McKenney wrote:
> > This commit adds s390.cat and s390.cfg files to allow users to check
> > litmus tests for s390-specific code. Note that this change only enables
> >
On Fri, Aug 31, 2018 at 05:06:30PM +0100, Will Deacon wrote:
> Hi Paul,
>
> On Wed, Aug 29, 2018 at 02:10:53PM -0700, Paul E. McKenney wrote:
> > This commit adds s390.cat and s390.cfg files to allow users to check
> > litmus tests for s390-specific code. Note that this change only enables
> >
As part of commit 9b85e95a3080 ("uio: Change return
type to vm_fault_t") in 4.19-rc1, this conversion
was missed. Now converted 'ret' to vm_fault_t type.
Signed-off-by: Souptick Joarder
---
drivers/uio/uio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/uio/uio.c
As part of commit 9b85e95a3080 ("uio: Change return
type to vm_fault_t") in 4.19-rc1, this conversion
was missed. Now converted 'ret' to vm_fault_t type.
Signed-off-by: Souptick Joarder
---
drivers/uio/uio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/uio/uio.c
1 - 100 of 310 matches
Mail list logo
