Copy the key mask to the right offset inside the shadow CRYCB
Signed-off-by: Pierre Morel
Reviewed-by: David Hildenbrand
Reviewed-by: Cornelia Huck
Reviewed-by: Janosch Frank
---
arch/s390/kvm/vsie.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/s390/kvm/vsie.c
Copy the key mask to the right offset inside the shadow CRYCB
Signed-off-by: Pierre Morel
Reviewed-by: David Hildenbrand
Reviewed-by: Cornelia Huck
Reviewed-by: Janosch Frank
---
arch/s390/kvm/vsie.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/s390/kvm/vsie.c
Then tracing syscall exit event it is extremely useful to filter exit
codes equal to some negative value, to react only to required errors.
But negative numbers does not work:
[root@snorch sys_exit_read]# echo "ret == -1" > filter
bash: echo: write error: Invalid argument
[root@snorch
Then tracing syscall exit event it is extremely useful to filter exit
codes equal to some negative value, to react only to required errors.
But negative numbers does not work:
[root@snorch sys_exit_read]# echo "ret == -1" > filter
bash: echo: write error: Invalid argument
[root@snorch
On Wed, 22 Aug 2018 15:16:19 -0400
Tony Krowiak wrote:
> One of the things I suggested in a private conversation with Christian
> earlier
> today was to provide an additional rw sysfs attribute - a boolean - that
> indicates
> whether all usage domains should also be control domains. The
On Wed, 22 Aug 2018 15:16:19 -0400
Tony Krowiak wrote:
> One of the things I suggested in a private conversation with Christian
> earlier
> today was to provide an additional rw sysfs attribute - a boolean - that
> indicates
> whether all usage domains should also be control domains. The
This patch adds adma_table_cnt member to struct sdhci_host to give more
flexibility to drivers to control the ADMA table count.
Default value of adma_table_cnt is set to (SDHCI_MAX_SEGS * 2 + 1).
Signed-off-by: Jisheng Zhang
---
drivers/mmc/host/sdhci.c | 17 +
This patch adds adma_table_cnt member to struct sdhci_host to give more
flexibility to drivers to control the ADMA table count.
Default value of adma_table_cnt is set to (SDHCI_MAX_SEGS * 2 + 1).
Signed-off-by: Jisheng Zhang
---
drivers/mmc/host/sdhci.c | 17 +
When using DMA, if the DMA addr spans 128MB boundary, we have to split
the DMA transfer into two so that each one doesn't exceed the boundary.
Signed-off-by: Jisheng Zhang
---
drivers/mmc/host/sdhci-of-dwcmshc.c | 39 +
1 file changed, 39 insertions(+)
diff --git
When using DMA, if the DMA addr spans 128MB boundary, we have to split
the DMA transfer into two so that each one doesn't exceed the boundary.
Signed-off-by: Jisheng Zhang
---
drivers/mmc/host/sdhci-of-dwcmshc.c | 39 +
1 file changed, 39 insertions(+)
diff --git
Linus,
please pull sound fixes for v4.19-rc1 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-fix-4.19-rc1
The topmost commit is 8a328ac1f9ebfc7621f76bbb27aa0382cc5b393d
sound fixes for 4.19-rc1
Linus,
please pull sound fixes for v4.19-rc1 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-fix-4.19-rc1
The topmost commit is 8a328ac1f9ebfc7621f76bbb27aa0382cc5b393d
sound fixes for 4.19-rc1
Add this hook so that it can be overridden with driver specific
implementations. We also let the original sdhci_adma_write_desc()
accept so that the function can set its new value. Then export
the function so that it could be reused by driver's specific
implementations.
Signed-off-by: Jisheng
Add this hook so that it can be overridden with driver specific
implementations. We also let the original sdhci_adma_write_desc()
accept so that the function can set its new value. Then export
the function so that it could be reused by driver's specific
implementations.
Signed-off-by: Jisheng
When using DMA, if the DMA addr spans 128MB boundary, we have to split
the DMA transfer into two so that each one doesn't exceed the boundary.
patch1 adds adma_table_num to struct sdhci_host so that driver can
control the ADMA table number.
patch2 introduces adma_write_desc() hook to struct
When using DMA, if the DMA addr spans 128MB boundary, we have to split
the DMA transfer into two so that each one doesn't exceed the boundary.
patch1 adds adma_table_num to struct sdhci_host so that driver can
control the ADMA table number.
patch2 introduces adma_write_desc() hook to struct
> Could you test this patch? I found that bug a month ago but didn't submit
> yet.
I don't have a reproducer now. I manually analzed a root cause of the
crash using a fuzzer's log. The log reported a race on 'alloc->vma'.
Because I don't have a reproducer, I can't test the patch. I'm sorry.
> Could you test this patch? I found that bug a month ago but didn't submit
> yet.
I don't have a reproducer now. I manually analzed a root cause of the
crash using a fuzzer's log. The log reported a race on 'alloc->vma'.
Because I don't have a reproducer, I can't test the patch. I'm sorry.
On 08/23/2018 09:44 AM, David Hildenbrand wrote:
On 22.08.2018 22:16, Tony Krowiak wrote:
On 08/22/2018 07:24 AM, David Hildenbrand wrote:
On 22.08.2018 13:19, David Hildenbrand wrote:
On 13.08.2018 23:48, Tony Krowiak wrote:
From: Tony Krowiak
Introduces a new CPU model feature and two
On 08/23/2018 09:44 AM, David Hildenbrand wrote:
On 22.08.2018 22:16, Tony Krowiak wrote:
On 08/22/2018 07:24 AM, David Hildenbrand wrote:
On 22.08.2018 13:19, David Hildenbrand wrote:
On 13.08.2018 23:48, Tony Krowiak wrote:
From: Tony Krowiak
Introduces a new CPU model feature and two
On Wed, Aug 22, 2018 at 05:31:04PM -0700, Dmitry Torokhov wrote:
> On Wed, Aug 22, 2018 at 5:21 PM Ryan Lee
> wrote:
> > + mdelay(10);
> Is it really necessary for the CPU to spin for 10msec here?
> usleep_range() would be better solution.
Or msleep() for that matter, it's not going ot
On Wed, Aug 22, 2018 at 05:31:04PM -0700, Dmitry Torokhov wrote:
> On Wed, Aug 22, 2018 at 5:21 PM Ryan Lee
> wrote:
> > + mdelay(10);
> Is it really necessary for the CPU to spin for 10msec here?
> usleep_range() would be better solution.
Or msleep() for that matter, it's not going ot
Hi.
2018-08-23 7:40 GMT+09:00 kbuild test robot :
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: 899fbc33fd775b9dfa363db28f322272920a2196
> commit: 0fbe9a245c60bedebb6dd329966f463bb724450a microblaze: add endianness
> options to LDFLAGS instead
Hi.
2018-08-23 7:40 GMT+09:00 kbuild test robot :
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: 899fbc33fd775b9dfa363db28f322272920a2196
> commit: 0fbe9a245c60bedebb6dd329966f463bb724450a microblaze: add endianness
> options to LDFLAGS instead
On Wed, Aug 22, 2018 at 11:32:26AM +0200, Oscar Salvador wrote:
> From: Oscar Salvador
>
> This patch tries to simplify node_states_check_changes_offline
> and make the code more understandable by:
>
> - Removing the if (N_MEMORY == N_NORMAL_MEMORY) wrong statement
> - Removing the if (N_MEMORY
On Wed, Aug 22, 2018 at 11:32:26AM +0200, Oscar Salvador wrote:
> From: Oscar Salvador
>
> This patch tries to simplify node_states_check_changes_offline
> and make the code more understandable by:
>
> - Removing the if (N_MEMORY == N_NORMAL_MEMORY) wrong statement
> - Removing the if (N_MEMORY
Steven,
commit 7f11a591bbdb111792298144c3476506aa7f1ca8 (HEAD -> v4.14.63-rt40-rebase,
tag: v4.14.63-rt40-rebase, origin/v4.14-rt-rebase)
Author: Steven Rostedt (VMware)
Date: Wed May 16 09:33:00 2018 -0400
Linux 4.14.63-rt40 REBASE
diff --git a/localversion-rt b/localversion-rt
index
Steven,
commit 7f11a591bbdb111792298144c3476506aa7f1ca8 (HEAD -> v4.14.63-rt40-rebase,
tag: v4.14.63-rt40-rebase, origin/v4.14-rt-rebase)
Author: Steven Rostedt (VMware)
Date: Wed May 16 09:33:00 2018 -0400
Linux 4.14.63-rt40 REBASE
diff --git a/localversion-rt b/localversion-rt
index
Hi guys,
(CC: +Fan Wu)
On 19/07/18 19:36, Tyler Baicar wrote:
> On 7/19/2018 10:46 AM, James Morse wrote:
>> On 19/07/18 15:01, Borislav Petkov wrote:
>>> On Mon, Jul 16, 2018 at 01:26:49PM -0400, Tyler Baicar wrote:
Enable per-layer error reporting for ARM systems so that the error
Hi guys,
(CC: +Fan Wu)
On 19/07/18 19:36, Tyler Baicar wrote:
> On 7/19/2018 10:46 AM, James Morse wrote:
>> On 19/07/18 15:01, Borislav Petkov wrote:
>>> On Mon, Jul 16, 2018 at 01:26:49PM -0400, Tyler Baicar wrote:
Enable per-layer error reporting for ARM systems so that the error
On 08/22/2018 09:16 PM, Tony Krowiak wrote:
On 08/22/2018 01:11 PM, Halil Pasic wrote:
On 08/22/2018 05:48 PM, Christian Borntraeger wrote:
On 08/22/2018 05:34 PM, Pierre Morel wrote:
On 22/08/2018 17:11, Christian Borntraeger wrote:
On 08/22/2018 01:03 PM, Pierre Morel wrote:
That's
On 08/22/2018 09:16 PM, Tony Krowiak wrote:
On 08/22/2018 01:11 PM, Halil Pasic wrote:
On 08/22/2018 05:48 PM, Christian Borntraeger wrote:
On 08/22/2018 05:34 PM, Pierre Morel wrote:
On 22/08/2018 17:11, Christian Borntraeger wrote:
On 08/22/2018 01:03 PM, Pierre Morel wrote:
That's
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: "Robin H. Johnson"
[ Upstream commit 2c4d6baf1bc4f7729773ffcee9ba2a9781578633 ]
The ec_no_wakeup matcher added for Thinkpad X1 Carbon 6th gen systems
beyond matched only a single DMI model
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: "Robin H. Johnson"
[ Upstream commit 2c4d6baf1bc4f7729773ffcee9ba2a9781578633 ]
The ec_no_wakeup matcher added for Thinkpad X1 Carbon 6th gen systems
beyond matched only a single DMI model
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Nicolas Boichat
[ Upstream commit 3e84c7651dde7cca43c5cfd7385086599cce5a5d ]
Another device in the hammer class, with USB id 0x5030.
Signed-off-by: Nicolas Boichat
Acked-by: Benjamin
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Nicolas Boichat
[ Upstream commit 3e84c7651dde7cca43c5cfd7385086599cce5a5d ]
Another device in the hammer class, with USB id 0x5030.
Signed-off-by: Nicolas Boichat
Acked-by: Benjamin
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Maciej Purski
[ Upstream commit ecba7cfa3afbe489288f2c819158b7402afd7ee9 ]
Current implementation of mode_valid() and mode_fixup() callbacks
handle packed pixel modes improperly.
Fix it by
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Maciej Purski
[ Upstream commit ecba7cfa3afbe489288f2c819158b7402afd7ee9 ]
Current implementation of mode_valid() and mode_fixup() callbacks
handle packed pixel modes improperly.
Fix it by
Commit-ID: 49836f7811f383d8613661fff110ce74f4710d52
Gitweb: https://git.kernel.org/tip/49836f7811f383d8613661fff110ce74f4710d52
Author: Jack Henschel
AuthorDate: Wed, 4 Jul 2018 14:13:45 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 20 Aug 2018 08:54:58 -0300
perf parser:
Commit-ID: 49836f7811f383d8613661fff110ce74f4710d52
Gitweb: https://git.kernel.org/tip/49836f7811f383d8613661fff110ce74f4710d52
Author: Jack Henschel
AuthorDate: Wed, 4 Jul 2018 14:13:45 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 20 Aug 2018 08:54:58 -0300
perf parser:
This patch adds the da7280 bindings doc and driver to the Dialog
Semiconductor support list.
Signed-off-by: Roy Im
---
v4: No changes.
v3: No changes.
v2: No changes.
MAINTAINERS |2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 544cac8..720f9fe
This patch adds the da7280 bindings doc and driver to the Dialog
Semiconductor support list.
Signed-off-by: Roy Im
---
v4: No changes.
v3: No changes.
v2: No changes.
MAINTAINERS |2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 544cac8..720f9fe
Adds support for the Dialog DA7280 LRA/ERM Haptic Driver with
multiple mode and integrated waveform memory and wideband support.
It communicates via an I2C bus to the device.
Signed-off-by: Roy Im
---
v4: Updated code as dt-bindings are changed.
v3: No changes.
v2: Fixed kbuild
From: Roy Im
This patch adds support for the Dialog DA7280 Haptic driver IC.
In this patch set the following is provided:
[PATCH V2 1/3] MAINTAINERS file update for DA7280
[PATCH V2 2/3] DA7280 DT Binding
[PATCH V2 3/3] DA7280 Driver
This patch applies against linux-next and v4.18
Thank you,
From: Roy Im
This patch adds support for the Dialog DA7280 Haptic driver IC.
In this patch set the following is provided:
[PATCH V2 1/3] MAINTAINERS file update for DA7280
[PATCH V2 2/3] DA7280 DT Binding
[PATCH V2 3/3] DA7280 Driver
This patch applies against linux-next and v4.18
Thank you,
Adds support for the Dialog DA7280 LRA/ERM Haptic Driver with
multiple mode and integrated waveform memory and wideband support.
It communicates via an I2C bus to the device.
Signed-off-by: Roy Im
---
v4: Updated code as dt-bindings are changed.
v3: No changes.
v2: Fixed kbuild
Add device tree binding information for DA7280 haptic driver.
Example bindings for DA7280 are added.
Signed-off-by: Roy Im
---
v4: Fixed commit message, properties.
v3: Fixed subject format.
v2: No changes
.../devicetree/bindings/input/dlg,da7280.txt | 101
1
Add device tree binding information for DA7280 haptic driver.
Example bindings for DA7280 are added.
Signed-off-by: Roy Im
---
v4: Fixed commit message, properties.
v3: Fixed subject format.
v2: No changes
.../devicetree/bindings/input/dlg,da7280.txt | 101
1
On 22.8.2018 16:10, Lothar Waßmann wrote:
Michal Vokáč wrote:
On 22.8.2018 13:17, Lothar Waßmann wrote:
Michal Vokáč wrote:
On 22.8.2018 08:14, Lothar Waßmann wrote:
Michal Vokáč wrote:
Output of the PWM block of i.MX SoCs is always zero volts when the block
is disabled. This
On 22.8.2018 16:10, Lothar Waßmann wrote:
Michal Vokáč wrote:
On 22.8.2018 13:17, Lothar Waßmann wrote:
Michal Vokáč wrote:
On 22.8.2018 08:14, Lothar Waßmann wrote:
Michal Vokáč wrote:
Output of the PWM block of i.MX SoCs is always zero volts when the block
is disabled. This
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
[ Upstream commit cbaf45a6be497c272e80500e4fd9bccdf20d5050 ]
On failing to allocate the required SPIs, the actual number of interrupts
should be freed and not its log2 value.
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
[ Upstream commit cbaf45a6be497c272e80500e4fd9bccdf20d5050 ]
On failing to allocate the required SPIs, the actual number of interrupts
should be freed and not its log2 value.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Vikas Gupta
[ Upstream commit c58387ab1614f6d7fb9e244f214b61e7631421fc ]
Fix bug in the error code path when bnxt_request_irq() returns failure.
bnxt_disable_napi() should not be called in
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Max Gurtuvoy
[ Upstream commit d68a90e148f5a82aa67654c5012071e31c0e4baa ]
Controllers that are not yet enabled should not really enforce keep alive
timeouts, but we still want to track a
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Max Gurtuvoy
[ Upstream commit d68a90e148f5a82aa67654c5012071e31c0e4baa ]
Controllers that are not yet enabled should not really enforce keep alive
timeouts, but we still want to track a
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Vikas Gupta
[ Upstream commit c58387ab1614f6d7fb9e244f214b61e7631421fc ]
Fix bug in the error code path when bnxt_request_irq() returns failure.
bnxt_disable_napi() should not be called in
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: "Robin H. Johnson"
[ Upstream commit 2c4d6baf1bc4f7729773ffcee9ba2a9781578633 ]
The ec_no_wakeup matcher added for Thinkpad X1 Carbon 6th gen systems
beyond matched only a single DMI model
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Josh Poimboeuf
[ Upstream commit 08b393d01c88aff27347ed2b1b354eb4db2f1532 ]
Since the following commit:
cd77849a69cf ("objtool: Fix GCC 8 cold subfunction detection for aliased
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Chan
[ Upstream commit 78f058a4aa0f2280dc4d45d2c4a95728398ef857 ]
The current code returns -ENOMEM and does not bother to set the output
parameters to 0 when no rings are available.
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: "Robin H. Johnson"
[ Upstream commit 2c4d6baf1bc4f7729773ffcee9ba2a9781578633 ]
The ec_no_wakeup matcher added for Thinkpad X1 Carbon 6th gen systems
beyond matched only a single DMI model
4.17-stable review patch. If anyone has any objections, please let me know.
--
From: Josh Poimboeuf
[ Upstream commit 08b393d01c88aff27347ed2b1b354eb4db2f1532 ]
Since the following commit:
cd77849a69cf ("objtool: Fix GCC 8 cold subfunction detection for aliased
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Chan
[ Upstream commit 78f058a4aa0f2280dc4d45d2c4a95728398ef857 ]
The current code returns -ENOMEM and does not bother to set the output
parameters to 0 when no rings are available.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
[ Upstream commit ec348020566009d3da9b99f07c05814d13969c78 ]
When I wrote the sigreturn test, I didn't realize that AMD's busted
IRET behavior was different from Intel's
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Casey Schaufler
[ Upstream commit 7b4e88434c4e7982fb053c49657e1c8bbb8692d9 ]
Smack: Mark inode instant in smack_task_to_inode
/proc clean-up in commit
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit 6613b6173dee098997229caf1f3b961c49da75e6 upstream.
When first DCCP packet is SYNC or SYNCACK, we insert a new conntrack
that has an un-initialized timeout value, i.e.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 45c180bc29babbedd6b8c01b975780ef44d9d09c upstream.
struct xfrm_userpolicy_type has two holes, so we should not
use C99 style initializer.
KMSAN report:
BUG: KMSAN:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Lutomirski
[ Upstream commit ec348020566009d3da9b99f07c05814d13969c78 ]
When I wrote the sigreturn test, I didn't realize that AMD's busted
IRET behavior was different from Intel's
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Casey Schaufler
[ Upstream commit 7b4e88434c4e7982fb053c49657e1c8bbb8692d9 ]
Smack: Mark inode instant in smack_task_to_inode
/proc clean-up in commit
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit 6613b6173dee098997229caf1f3b961c49da75e6 upstream.
When first DCCP packet is SYNC or SYNCACK, we insert a new conntrack
that has an un-initialized timeout value, i.e.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 45c180bc29babbedd6b8c01b975780ef44d9d09c upstream.
struct xfrm_userpolicy_type has two holes, so we should not
use C99 style initializer.
KMSAN report:
BUG: KMSAN:
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Dinh Nguyen
[ Upstream commit bc8a2d9bcbf1ca548b1deb315d14e1da81945bea ]
The Stratix10 platform has an additional reset line, OCP(Open Core Protocol),
that also needs to get deasserted for the
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Dinh Nguyen
[ Upstream commit bc8a2d9bcbf1ca548b1deb315d14e1da81945bea ]
The Stratix10 platform has an additional reset line, OCP(Open Core Protocol),
that also needs to get deasserted for the
This is the start of the stable review cycle for the 4.18.5 release.
There are 22 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sat Aug 25 07:47:43 UTC 2018.
Anything
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Li RongQing
[ Upstream commit 7892bd081045222b9e4027fec279a28d6fe7aa66 ]
if dev_get_valid_name failed, propagate its return code
and remove the setting err to ENODEV, it will be set to
0
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jann Horn
commit a13f085d111e90469faf2d9965eb39b11c114d7e upstream.
This fixes the following issues:
- When a buffer size is supplied to reiserfs_listxattr() such that each
individual name
This is the start of the stable review cycle for the 4.18.5 release.
There are 22 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sat Aug 25 07:47:43 UTC 2018.
Anything
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Li RongQing
[ Upstream commit 7892bd081045222b9e4027fec279a28d6fe7aa66 ]
if dev_get_valid_name failed, propagate its return code
and remove the setting err to ENODEV, it will be set to
0
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jann Horn
commit a13f085d111e90469faf2d9965eb39b11c114d7e upstream.
This fixes the following issues:
- When a buffer size is supplied to reiserfs_listxattr() such that each
individual name
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Hansen
commit c40a56a7818cfe735fc93a69e1875f8bba834483 upstream.
The kernel image is mapped into two places in the virtual address space
(addresses without KASLR, of course):
1.
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Ellerman
commit 6d44acae1937b81cf8115ada8958e04f601f3f2e upstream.
When I added the spectre_v2 information in sysfs, I included the
availability of the ori31 speculation barrier.
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Hansen
commit c40a56a7818cfe735fc93a69e1875f8bba834483 upstream.
The kernel image is mapped into two places in the virtual address space
(addresses without KASLR, of course):
1.
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Ellerman
commit 6d44acae1937b81cf8115ada8958e04f601f3f2e upstream.
When I added the spectre_v2 information in sysfs, I included the
availability of the ori31 speculation barrier.
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Hansen
commit 6ea2738e0ca0e626c75202fb051c1e88d7a950fa upstream.
When chunks of the kernel image are freed, free_init_pages() is used
directly. Consolidate the three sites that do this.
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Zachary Zhang
commit 91a2968e245d6ba616db37001fa1a043078b1a65 upstream.
The PCIE I/O and MEM resource allocation mechanism is that root bus
goes through the following steps:
1. Check PCI
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Hansen
commit 0d83432811f26871295a9bc24d3c387924da6071 upstream.
free_reserved_area() takes pointers as arguments to show which addresses
should be freed. However, it does this in a
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Myron Stowe
commit 3dbe97efe8bf450b183d6dee2305cbc032e6b8a4 upstream.
PCIe r4.0, sec 9.3.5.4, "Device Control Register", shows both
Max_Payload_Size (MPS) and Max_Read_request_Size (MRRS) to
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Gustavo A. R. Silva
commit de5372da605d3bca46e3102bab51b7e1c0e0a6f6 upstream.
info.index can be indirectly controlled by user-space, hence leading
to a potential exploitation of the Spectre
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Hansen
commit 9f515cdb411ef34f1aaf4c40bb0c932cf6db5de1 upstream.
The x86 code has several places where it frees parts of kernel image:
1. Unused SMP alternative
2. __init code
3. The
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Hansen
commit 6ea2738e0ca0e626c75202fb051c1e88d7a950fa upstream.
When chunks of the kernel image are freed, free_init_pages() is used
directly. Consolidate the three sites that do this.
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Zachary Zhang
commit 91a2968e245d6ba616db37001fa1a043078b1a65 upstream.
The PCIE I/O and MEM resource allocation mechanism is that root bus
goes through the following steps:
1. Check PCI
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Hansen
commit 0d83432811f26871295a9bc24d3c387924da6071 upstream.
free_reserved_area() takes pointers as arguments to show which addresses
should be freed. However, it does this in a
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Myron Stowe
commit 3dbe97efe8bf450b183d6dee2305cbc032e6b8a4 upstream.
PCIe r4.0, sec 9.3.5.4, "Device Control Register", shows both
Max_Payload_Size (MPS) and Max_Read_request_Size (MRRS) to
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Gustavo A. R. Silva
commit de5372da605d3bca46e3102bab51b7e1c0e0a6f6 upstream.
info.index can be indirectly controlled by user-space, hence leading
to a potential exploitation of the Spectre
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Hansen
commit 9f515cdb411ef34f1aaf4c40bb0c932cf6db5de1 upstream.
The x86 code has several places where it frees parts of kernel image:
1. Unused SMP alternative
2. __init code
3. The
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jeremy Cline
commit 1a5d5e5d51e75a5bca67dadbcea8c841934b7b85 upstream.
'ac->ac_g_ex.fe_len' is a user-controlled value which is used in the
derivation of 'ac->ac_2order'. 'ac->ac_2order', in
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jeremy Cline
commit 1a5d5e5d51e75a5bca67dadbcea8c841934b7b85 upstream.
'ac->ac_g_ex.fe_len' is a user-controlled value which is used in the
derivation of 'ac->ac_2order'. 'ac->ac_2order', in
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit c463a158cb6c5d9a85b7d894cd4f8116e8bd6be0 upstream.
acpi_gsb_i2c_write_bytes() returns i2c_transfer()'s return value, which
is the number of transfers executed on success,
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Matthijs van Duin
commit 36ecc1481dc8d8c52d43ba18c6b642c1d2fde789 upstream.
It was being ignored because the flags were not passed to fd allocation.
Fixes: 54ebbfb16034 ("tty: add
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Lukas Wunner
commit 1204e35bedf4e5015cda559ed8c84789a6dae24e upstream.
Commit b440bde74f04 ("PCI: Add pci_ignore_hotplug() to ignore hotplug
events for a device") iterates over the devices on
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Lukas Wunner
commit 281e878eab191cce4259abbbf1a0322e3adae02c upstream.
When pciehp is unbound (e.g. on unplug of a Thunderbolt device), the
hotplug_slot struct is deregistered and thus freed
801 - 900 of 2464 matches
Mail list logo
