From: Frank Rowand
When an overlay is applied or removed, the live devicetree visible in
/proc/device-tree/, aka /sys/firmware/devicetree/base/, reflects the
changes. There is no method for user space to determine whether the
live devicetree was modified by overlay actions.
Provide a sysfs
From: Frank Rowand
When an overlay is applied or removed, the live devicetree visible in
/proc/device-tree/, aka /sys/firmware/devicetree/base/, reflects the
changes. There is no method for user space to determine whether the
live devicetree was modified by overlay actions.
Provide a sysfs
In push_rt_task(), we call pick_next_pushable_task() to pick
next_task before the check. If next_task and rq->curr are equal,
which will trigger BUG_ON() in pick_next_pushable_task(). See
the following code in pick_next_pushable_task().
static struct task_struct *pick_next_pushable_task(struct
In push_rt_task(), we call pick_next_pushable_task() to pick
next_task before the check. If next_task and rq->curr are equal,
which will trigger BUG_ON() in pick_next_pushable_task(). See
the following code in pick_next_pushable_task().
static struct task_struct *pick_next_pushable_task(struct
Looks like I accidentally rebased the fixes branch locally after
merging that patch in. Will fixup, thanks for reporting.
-Olof
On Fri, Nov 2, 2018 at 8:58 PM Stephen Rothwell wrote:
>
> Hi all,
>
> Commit
>
> cda58c80fe27 ("ARM: OMAP1: ams-delta: Fix impossible .irq < 0")
>
> is missing a
Looks like I accidentally rebased the fixes branch locally after
merging that patch in. Will fixup, thanks for reporting.
-Olof
On Fri, Nov 2, 2018 at 8:58 PM Stephen Rothwell wrote:
>
> Hi all,
>
> Commit
>
> cda58c80fe27 ("ARM: OMAP1: ams-delta: Fix impossible .irq < 0")
>
> is missing a
On Fri 02 Nov 17:57 PDT 2018, Niklas Cassel wrote:
> The apcs node has #clock-cells = <0>, which means that those who
> references it should specify 0 arguments.
>
> The apcs reference in the cpu node incorrectly specifies an argument,
> remove this bogus argument.
>
> Fixes: 65afdf458360
On Fri 02 Nov 17:57 PDT 2018, Niklas Cassel wrote:
> The apcs node has #clock-cells = <0>, which means that those who
> references it should specify 0 arguments.
>
> The apcs reference in the cpu node incorrectly specifies an argument,
> remove this bogus argument.
>
> Fixes: 65afdf458360
Replaced kmalloc_node + memset with kzalloc_node
Signed-off-by: Sabyasachi Gupta
---
arch/sparc/kernel/iommu.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/sparc/kernel/iommu.c b/arch/sparc/kernel/iommu.c
index 40d008b..05eb016 100644
---
Replaced kmalloc_node + memset with kzalloc_node
Signed-off-by: Sabyasachi Gupta
---
arch/sparc/kernel/iommu.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/sparc/kernel/iommu.c b/arch/sparc/kernel/iommu.c
index 40d008b..05eb016 100644
---
On Thu, Nov 01, 2018 at 09:13:07AM -0700, Paul E. McKenney wrote:
> On Wed, Oct 31, 2018 at 10:00:19PM -0700, Joel Fernandes wrote:
> > On Wed, Oct 31, 2018 at 11:17:48AM -0700, Paul E. McKenney wrote:
> > > On Tue, Oct 30, 2018 at 06:11:19PM -0700, Joel Fernandes wrote:
> > > > Hi Paul,
> > > >
On Thu, Nov 01, 2018 at 09:13:07AM -0700, Paul E. McKenney wrote:
> On Wed, Oct 31, 2018 at 10:00:19PM -0700, Joel Fernandes wrote:
> > On Wed, Oct 31, 2018 at 11:17:48AM -0700, Paul E. McKenney wrote:
> > > On Tue, Oct 30, 2018 at 06:11:19PM -0700, Joel Fernandes wrote:
> > > > Hi Paul,
> > > >
On Sat, Nov 3, 2018 at 10:31 AM Souptick Joarder wrote:
>
> Page fault handlers are supposed to return VM_FAULT codes,
> but some drivers/file systems mistakenly return error
> numbers. Now that all drivers/file systems have been converted
> to use the vm_fault_t return type, change the type
On Sat, Nov 3, 2018 at 10:31 AM Souptick Joarder wrote:
>
> Page fault handlers are supposed to return VM_FAULT codes,
> but some drivers/file systems mistakenly return error
> numbers. Now that all drivers/file systems have been converted
> to use the vm_fault_t return type, change the type
Page fault handlers are supposed to return VM_FAULT codes,
but some drivers/file systems mistakenly return error
numbers. Now that all drivers/file systems have been converted
to use the vm_fault_t return type, change the type definition
to no longer be compatible with 'int'. By making it an
Page fault handlers are supposed to return VM_FAULT codes,
but some drivers/file systems mistakenly return error
numbers. Now that all drivers/file systems have been converted
to use the vm_fault_t return type, change the type definition
to no longer be compatible with 'int'. By making it an
Hi Rob,
First, the point of this patch was to provide a way for userspace (program,
command line interface, whatever -- that is orthogonal) to ensure that its
view of the devicetree via /proc/device-tree/ is consistent since an overlay
apply or remove can alter the devicetree.
For in-kernel use,
Hi Rob,
First, the point of this patch was to provide a way for userspace (program,
command line interface, whatever -- that is orthogonal) to ensure that its
view of the devicetree via /proc/device-tree/ is consistent since an overlay
apply or remove can alter the devicetree.
For in-kernel use,
Move tpm_validate_command() to tpm2-space.c and make it part of the
tpm2_prepare_space() flow. Make cc resolution as part of the TPM space
functionality in order to detach it from rest of the tpm_transmit()
flow.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-interface.c | 72
Instead of accessing fields of the command header through offsets to
the raw buffer, it is a better idea to use the header struct pointer
that is already used elsewhere in the function.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-interface.c | 4 ++--
1 file changed, 2
Encapsulate tpm_transmit() call pattern to tpm_dev_transmit() because it
is identically used from two places. Use unlocked version of
tpm_transmit() so that we are able to move the calls to
tpm2_prepare_space() and tpm2_commit_space() later on to this new
function.
Signed-off-by: Jarkko Sakkinen
Move tpm_validate_command() to tpm2-space.c and make it part of the
tpm2_prepare_space() flow. Make cc resolution as part of the TPM space
functionality in order to detach it from rest of the tpm_transmit()
flow.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-interface.c | 72
Instead of accessing fields of the command header through offsets to
the raw buffer, it is a better idea to use the header struct pointer
that is already used elsewhere in the function.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-interface.c | 4 ++--
1 file changed, 2
Encapsulate tpm_transmit() call pattern to tpm_dev_transmit() because it
is identically used from two places. Use unlocked version of
tpm_transmit() so that we are able to move the calls to
tpm2_prepare_space() and tpm2_commit_space() later on to this new
function.
Signed-off-by: Jarkko Sakkinen
Prepare and commit TPM space before and after calling tpm_transmit()
instead of doing that inside tpm_transmit(). After this change we can
remove TPM_TRANSMIT_NESTED flag.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-dev-common.c | 31 ---
Prepare and commit TPM space before and after calling tpm_transmit()
instead of doing that inside tpm_transmit(). After this change we can
remove TPM_TRANSMIT_NESTED flag.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-dev-common.c | 31 ---
Since we pass an initialized struct tpm_buf instance in every call site
now, it is cleaner to pass that directly to the tpm_transmit_cmd() as
the TPM command/response buffer.
Fine-tune a little bit tpm_transmit() and tpm_transmit_cmd() comments
while doing this.
Signed-off-by: Jarkko Sakkinen
Make the changes that are needed to detach TPM space code from
tpm_transmit() flow so that we do no longer need nested tpm_transmit()
calls.
Jarkko Sakkinen (6):
tpm: use tpm_buf in tpm_transmit_cmd() as the IO parameter
tpm: clean up tpm_try_transmit() error handling flow
tpm: access
Move locking, locality handling and power management to tpm_transmit()
in order to simplify the flow and fix the error message formatting in
tpm_try_transmit() to output correct function name by using the
'__func__' macro.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-interface.c |
Since we pass an initialized struct tpm_buf instance in every call site
now, it is cleaner to pass that directly to the tpm_transmit_cmd() as
the TPM command/response buffer.
Fine-tune a little bit tpm_transmit() and tpm_transmit_cmd() comments
while doing this.
Signed-off-by: Jarkko Sakkinen
Make the changes that are needed to detach TPM space code from
tpm_transmit() flow so that we do no longer need nested tpm_transmit()
calls.
Jarkko Sakkinen (6):
tpm: use tpm_buf in tpm_transmit_cmd() as the IO parameter
tpm: clean up tpm_try_transmit() error handling flow
tpm: access
Move locking, locality handling and power management to tpm_transmit()
in order to simplify the flow and fix the error message formatting in
tpm_try_transmit() to output correct function name by using the
'__func__' macro.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-interface.c |
Hi all,
Commit
cda58c80fe27 ("ARM: OMAP1: ams-delta: Fix impossible .irq < 0")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpe0FrniLfHl.pgp
Description: OpenPGP digital signature
Hi all,
Commit
cda58c80fe27 ("ARM: OMAP1: ams-delta: Fix impossible .irq < 0")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpe0FrniLfHl.pgp
Description: OpenPGP digital signature
On 11/1/18 8:11 PM, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 4ed591c8ab44e711e56b8e021ffaf4f407c045f5 ("net/ipv6: Allow onlink
> routes to have a device mismatch if it is the default route")
>
On 11/1/18 8:11 PM, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 4ed591c8ab44e711e56b8e021ffaf4f407c045f5 ("net/ipv6: Allow onlink
> routes to have a device mismatch if it is the default route")
>
Hello Dear
how are you doing today? my name is Bruce Blake, the manager foreign affairs in
City Finance Bank, we have a customer here in bank that has not accessed his
account for the past 18 years, after some research made about him we found out
he was a victim of the crashed mining company
Hello Dear
how are you doing today? my name is Bruce Blake, the manager foreign affairs in
City Finance Bank, we have a customer here in bank that has not accessed his
account for the past 18 years, after some research made about him we found out
he was a victim of the crashed mining company
Hello Stephen,
On 11/2/2018 10:08 PM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-28 00:35:40)
Add support for the lpass clock controller found on SDM845 based devices.
This would allow lpass peripheral loader drivers to control the clocks to
bring the subsystem out of reset.
LPASS clocks
Hello Stephen,
On 11/2/2018 10:08 PM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-28 00:35:40)
Add support for the lpass clock controller found on SDM845 based devices.
This would allow lpass peripheral loader drivers to control the clocks to
bring the subsystem out of reset.
LPASS clocks
Hello Stephen,
On 10/18/2018 5:02 AM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-11 04:36:01)
--- a/drivers/cpufreq/Kconfig.arm
+++ b/drivers/cpufreq/Kconfig.arm
@@ -121,6 +121,17 @@ config ARM_QCOM_CPUFREQ_KRYO
If in doubt, say N.
+config ARM_QCOM_CPUFREQ_HW
+ bool
Hello Stephen,
On 10/18/2018 5:02 AM, Stephen Boyd wrote:
Quoting Taniya Das (2018-10-11 04:36:01)
--- a/drivers/cpufreq/Kconfig.arm
+++ b/drivers/cpufreq/Kconfig.arm
@@ -121,6 +121,17 @@ config ARM_QCOM_CPUFREQ_KRYO
If in doubt, say N.
+config ARM_QCOM_CPUFREQ_HW
+ bool
In create_filter(), pe variable is leaked.
Since commit 80765597bc58 ("tracing: Rewrite filter logic to be simpler
and faster"), create_filter_finish() is missing.
kmemleak:
unreferenced object 0x90148ba9c790 (size 8):
comm "bash", pid 1378, jiffies 4294731025 (age 15.258s)
hex dump
In create_filter(), pe variable is leaked.
Since commit 80765597bc58 ("tracing: Rewrite filter logic to be simpler
and faster"), create_filter_finish() is missing.
kmemleak:
unreferenced object 0x90148ba9c790 (size 8):
comm "bash", pid 1378, jiffies 4294731025 (age 15.258s)
hex dump
On Fri, Nov 02, 2018 at 04:28:04PM -0700, Josh Hunt wrote:
On Fri, Nov 2, 2018 at 12:00 PM Greg Kroah-Hartman
wrote:
4.14-stable review patch. If anyone has any objections, please let me know.
--
Upstream commit bffa72cf7f9d ("net: sk_buff rbnode reorg") got
backported as
On Fri, Nov 02, 2018 at 04:28:04PM -0700, Josh Hunt wrote:
On Fri, Nov 2, 2018 at 12:00 PM Greg Kroah-Hartman
wrote:
4.14-stable review patch. If anyone has any objections, please let me know.
--
Upstream commit bffa72cf7f9d ("net: sk_buff rbnode reorg") got
backported as
On Fri, Nov 02, 2018 at 07:56:57PM +, Sudip Mukherjee wrote:
Hi Greg,
On Fri, Nov 2, 2018 at 6:53 PM Greg Kroah-Hartman
wrote:
4.14-stable review patch. If anyone has any objections, please let me know.
It seems this has already been reverted upstream:
9bf4e370048d ("ARM: dts:
On Fri, Nov 02, 2018 at 07:56:57PM +, Sudip Mukherjee wrote:
Hi Greg,
On Fri, Nov 2, 2018 at 6:53 PM Greg Kroah-Hartman
wrote:
4.14-stable review patch. If anyone has any objections, please let me know.
It seems this has already been reverted upstream:
9bf4e370048d ("ARM: dts:
On Fri, Nov 02, 2018 at 07:59:39PM +, Sudip Mukherjee wrote:
Hi Greg,
On Fri, Nov 2, 2018 at 6:52 PM Greg Kroah-Hartman
wrote:
4.14-stable review patch. If anyone has any objections, please let me know.
There is another upstream patch which fixes this one.
e3ca34880652 ("net/mlx5: Fix
On 2018/11/02 22:36, Peter Zijlstra wrote:
> On Fri, Nov 02, 2018 at 10:31:57PM +0900, Tetsuo Handa wrote:
>> syzbot is sometimes getting mixed output like below due to concurrent
>> printk(). Mitigate such output by using line-buffered printk() API.
>>
>> RCU used illegally from idle CPU!
>>
On Fri, Nov 02, 2018 at 07:59:39PM +, Sudip Mukherjee wrote:
Hi Greg,
On Fri, Nov 2, 2018 at 6:52 PM Greg Kroah-Hartman
wrote:
4.14-stable review patch. If anyone has any objections, please let me know.
There is another upstream patch which fixes this one.
e3ca34880652 ("net/mlx5: Fix
On 2018/11/02 22:36, Peter Zijlstra wrote:
> On Fri, Nov 02, 2018 at 10:31:57PM +0900, Tetsuo Handa wrote:
>> syzbot is sometimes getting mixed output like below due to concurrent
>> printk(). Mitigate such output by using line-buffered printk() API.
>>
>> RCU used illegally from idle CPU!
>>
From: Eric Biggers
syzbot hit the 'BUG_ON(index_key->desc_len == 0);' in __key_link_begin()
called from construct_alloc_key() during sys_request_key(), because the
length of the key description was never calculated.
The problem is that we rely on ->desc_len being initialized by
From: Eric Biggers
syzbot hit the 'BUG_ON(index_key->desc_len == 0);' in __key_link_begin()
called from construct_alloc_key() during sys_request_key(), because the
length of the key description was never calculated.
The problem is that we rely on ->desc_len being initialized by
On Fri, Nov 02, 2018 at 04:15:10PM -0700, Eric Biggers wrote:
> From: Eric Biggers
>
> syzbot hit the 'BUG_ON(index_key->desc_len == 0);' in __key_link_begin()
> called from construct_alloc_key() during sys_request_key(), because the
> length of the key description was never calculated.
>
> The
On Fri, Nov 02, 2018 at 04:15:10PM -0700, Eric Biggers wrote:
> From: Eric Biggers
>
> syzbot hit the 'BUG_ON(index_key->desc_len == 0);' in __key_link_begin()
> called from construct_alloc_key() during sys_request_key(), because the
> length of the key description was never calculated.
>
> The
On 2018/11/02 23:40, Matthew Wilcox wrote:
> On Fri, Nov 02, 2018 at 10:31:55PM +0900, Tetsuo Handa wrote:
>> get_printk_buffer() tries to assign a "struct printk_buffer" from
>> statically preallocated array. get_printk_buffer() returns NULL if
>> all "struct printk_buffer" are in use, but
On 2018/11/02 23:40, Matthew Wilcox wrote:
> On Fri, Nov 02, 2018 at 10:31:55PM +0900, Tetsuo Handa wrote:
>> get_printk_buffer() tries to assign a "struct printk_buffer" from
>> statically preallocated array. get_printk_buffer() returns NULL if
>> all "struct printk_buffer" are in use, but
Move tpm_validate_command() to tpm2-space.c and make it part of the
tpm2_prepare_space() flow. Make cc resolution as part of the TPM space
functionality in order to detach it from rest of the tpm_transmit()
flow.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-interface.c | 72
Move tpm_validate_command() to tpm2-space.c and make it part of the
tpm2_prepare_space() flow. Make cc resolution as part of the TPM space
functionality in order to detach it from rest of the tpm_transmit()
flow.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-interface.c | 72
On 2018-11-02 16:11, Jarkko Sakkinen wrote:
diff --git a/arch/x86/kernel/cpu/intel_sgx.c b/arch/x86/kernel/cpu/intel_sgx.c
new file mode 100644
index ..b86aa4111592
--- /dev/null
+++ b/arch/x86/kernel/cpu/intel_sgx.c
...
+static __init int sgx_page_cache_init(void)
+{
+ u32
On 2018-11-02 16:11, Jarkko Sakkinen wrote:
diff --git a/arch/x86/kernel/cpu/intel_sgx.c b/arch/x86/kernel/cpu/intel_sgx.c
new file mode 100644
index ..b86aa4111592
--- /dev/null
+++ b/arch/x86/kernel/cpu/intel_sgx.c
...
+static __init int sgx_page_cache_init(void)
+{
+ u32
The apcs node has #clock-cells = <0>, which means that those who
references it should specify 0 arguments.
The apcs reference in the cpu node incorrectly specifies an argument,
remove this bogus argument.
Fixes: 65afdf458360 ("arm64: dts: qcom: msm8916: Add CPU frequency scaling
support")
The apcs node has #clock-cells = <0>, which means that those who
references it should specify 0 arguments.
The apcs reference in the cpu node incorrectly specifies an argument,
remove this bogus argument.
Fixes: 65afdf458360 ("arm64: dts: qcom: msm8916: Add CPU frequency scaling
support")
Instead of accessing fields of the command header through offsets to
the raw buffer, it is a better idea to use the header struct pointer
that is already used elsewhere in the function.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-interface.c | 4 ++--
1 file changed, 2
Instead of accessing fields of the command header through offsets to
the raw buffer, it is a better idea to use the header struct pointer
that is already used elsewhere in the function.
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-interface.c | 4 ++--
1 file changed, 2
Add ARM64-specific code to enable Hyper-V. This code includes:
* Detecting Hyper-V and initializing the guest/Hyper-V interface
* Setting up Hyper-V's synthetic clocks
* Making hypercalls using the HVC instruction
* Setting up VMbus and stimer0 interrupts
* Setting up kexec and crash handlers
This
hyperv-tlfs.h defines Hyper-V interfaces from the Hyper-V Top Level
Functional Spec (TLFS). The TLFS is distinctly oriented to x86/x64,
and Hyper-V has not separated out the architecture-dependent parts into
x86/x64 vs. ARM64. So hyperv-tlfs.h includes information for ARM64
that is not yet
Add ARM64-specific code to enable Hyper-V. This code includes:
* Detecting Hyper-V and initializing the guest/Hyper-V interface
* Setting up Hyper-V's synthetic clocks
* Making hypercalls using the HVC instruction
* Setting up VMbus and stimer0 interrupts
* Setting up kexec and crash handlers
This
hyperv-tlfs.h defines Hyper-V interfaces from the Hyper-V Top Level
Functional Spec (TLFS). The TLFS is distinctly oriented to x86/x64,
and Hyper-V has not separated out the architecture-dependent parts into
x86/x64 vs. ARM64. So hyperv-tlfs.h includes information for ARM64
that is not yet
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, and are needed by Linux guests on Hyper-V on ARM64. The
x86/x64 implementation is null because VMbus interrupts on x86/x64
don't use an IRQ.
Signed-off-by:
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, and are needed by Linux guests on Hyper-V on ARM64. The
x86/x64 implementation is null because VMbus interrupts on x86/x64
don't use an IRQ.
Signed-off-by:
Update drivers/hv/Kconfig so CONFIG_HYPERV can be selected on ARM64,
causing the Hyper-V specific code to be built.
Signed-off-by: Michael Kelley
---
drivers/hv/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/hv/Kconfig b/drivers/hv/Kconfig
index
This series enables Linux guests running on Hyper-V on ARM64
hardware. New ARM64-specific code in arch/arm64/hyperv initializes
Hyper-V, including its synthetic clocks and hypercall mechanism.
Existing architecture independent drivers for Hyper-V's VMbus and
synthetic devices just work when built
Update drivers/hv/Kconfig so CONFIG_HYPERV can be selected on ARM64,
causing the Hyper-V specific code to be built.
Signed-off-by: Michael Kelley
---
drivers/hv/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/hv/Kconfig b/drivers/hv/Kconfig
index
This series enables Linux guests running on Hyper-V on ARM64
hardware. New ARM64-specific code in arch/arm64/hyperv initializes
Hyper-V, including its synthetic clocks and hypercall mechanism.
Existing architecture independent drivers for Hyper-V's VMbus and
synthetic devices just work when built
Regression fix for net/9p handling of iov_iter; broken
by braino when switching to iov_iter_is_kvec() et.al., spotted
and fixed by Marc.
The following changes since commit 0e9b4a82710220c04100892fb7277b78fd33a747:
missing bits of "iov_iter: Separate type from direction and use accessor
Regression fix for net/9p handling of iov_iter; broken
by braino when switching to iov_iter_is_kvec() et.al., spotted
and fixed by Marc.
The following changes since commit 0e9b4a82710220c04100892fb7277b78fd33a747:
missing bits of "iov_iter: Separate type from direction and use accessor
On Fri, Nov 02, 2018 at 04:56:58PM +0100, Arnd Bergmann wrote:
> When CONFIG_CC_OPTIMIZE_FOR_DEBUGGING is set, we get countless warnings
> like
>
> In function 'check_copy_size',
> inlined from 'copy_from_user' at include/linux/uaccess.h:146:6,
> inlined from '__copy_siginfo_from_user' at
On Fri, Nov 02, 2018 at 04:56:58PM +0100, Arnd Bergmann wrote:
> When CONFIG_CC_OPTIMIZE_FOR_DEBUGGING is set, we get countless warnings
> like
>
> In function 'check_copy_size',
> inlined from 'copy_from_user' at include/linux/uaccess.h:146:6,
> inlined from '__copy_siginfo_from_user' at
On Fri, Nov 02, 2018 at 04:54:25PM +0100, Arnd Bergmann wrote:
> On 11/2/18, Masahiro Yamada wrote:
> > On Thu, Nov 1, 2018 at 11:32 PM Changbin Du wrote:
> >> On Thu, Nov 01, 2018 at 12:32:48PM +0900, Masahiro Yamada wrote:
> >
> > How about clang?
> >
> > For clang, -Og might be equivalent to
Hi Yamada,
>On Fri, Nov 02, 2018 at 05:25:00PM +0900, Masahiro Yamada wrote:
>[...]
> > > >
> > > > diff --git a/drivers/virt/vboxguest/vboxguest_core.c
> > > > b/drivers/virt/vboxguest/vboxguest_core.c
> > > > index 3093655c7b92..1475ed5ffcde 100644
> > > > ---
On Fri, Nov 02, 2018 at 04:54:25PM +0100, Arnd Bergmann wrote:
> On 11/2/18, Masahiro Yamada wrote:
> > On Thu, Nov 1, 2018 at 11:32 PM Changbin Du wrote:
> >> On Thu, Nov 01, 2018 at 12:32:48PM +0900, Masahiro Yamada wrote:
> >
> > How about clang?
> >
> > For clang, -Og might be equivalent to
Hi Yamada,
>On Fri, Nov 02, 2018 at 05:25:00PM +0900, Masahiro Yamada wrote:
>[...]
> > > >
> > > > diff --git a/drivers/virt/vboxguest/vboxguest_core.c
> > > > b/drivers/virt/vboxguest/vboxguest_core.c
> > > > index 3093655c7b92..1475ed5ffcde 100644
> > > > ---
On Sat, Nov 03, 2018 at 12:33:01AM +0100, Borislav Petkov wrote:
> On Sat, Nov 03, 2018 at 01:11:01AM +0200, Jarkko Sakkinen wrote:
> > From: Kai Huang
> >
> > X86_FEATURE_SGX reflects whether or not the CPU supports Intel's
> > Software Guard eXtensions (SGX).
> >
> > Signed-off-by: Kai Huang
On Sat, Nov 03, 2018 at 12:33:01AM +0100, Borislav Petkov wrote:
> On Sat, Nov 03, 2018 at 01:11:01AM +0200, Jarkko Sakkinen wrote:
> > From: Kai Huang
> >
> > X86_FEATURE_SGX reflects whether or not the CPU supports Intel's
> > Software Guard eXtensions (SGX).
> >
> > Signed-off-by: Kai Huang
On Fri, Nov 02, 2018 at 10:39:59AM -0700, Luck, Tony wrote:
> On Fri, Nov 02, 2018 at 05:10:13PM +0100, Borislav Petkov wrote:
> > On Fri, Nov 02, 2018 at 04:32:06PM +0100, Arnd Bergmann wrote:
> > > We cannot currently select ACPI_ADXL without also enabling the top-level
> > > ACPI option:
> > >
On Fri, Nov 02, 2018 at 10:39:59AM -0700, Luck, Tony wrote:
> On Fri, Nov 02, 2018 at 05:10:13PM +0100, Borislav Petkov wrote:
> > On Fri, Nov 02, 2018 at 04:32:06PM +0100, Arnd Bergmann wrote:
> > > We cannot currently select ACPI_ADXL without also enabling the top-level
> > > ACPI option:
> > >
On 10/22/18 7:59 AM, Steve Sistare wrote:
When a CPU has no more CFS tasks to run, and idle_balance() fails to
find a task, then attempt to steal a task from an overloaded CPU in the
same LLC. Maintain and use a bitmap of overloaded CPUs to efficiently
identify candidates. To minimize search
On 10/22/18 7:59 AM, Steve Sistare wrote:
When a CPU has no more CFS tasks to run, and idle_balance() fails to
find a task, then attempt to steal a task from an overloaded CPU in the
same LLC. Maintain and use a bitmap of overloaded CPUs to efficiently
identify candidates. To minimize search
On Sat, Nov 3, 2018 at 12:32 AM Andy Lutomirski wrote:
> On Fri, Nov 2, 2018 at 4:28 PM Jann Horn wrote:
> > On Fri, Nov 2, 2018 at 11:04 PM Sean Christopherson
> > wrote:
> > > On Fri, Nov 02, 2018 at 08:02:23PM +0100, Jann Horn wrote:
> > > > On Fri, Nov 2, 2018 at 7:27 PM Sean Christopherson
On Sat, Nov 3, 2018 at 12:32 AM Andy Lutomirski wrote:
> On Fri, Nov 2, 2018 at 4:28 PM Jann Horn wrote:
> > On Fri, Nov 2, 2018 at 11:04 PM Sean Christopherson
> > wrote:
> > > On Fri, Nov 02, 2018 at 08:02:23PM +0100, Jann Horn wrote:
> > > > On Fri, Nov 2, 2018 at 7:27 PM Sean Christopherson
On Fri, Nov 02, 2018 at 09:35:23AM -0700, Linus Torvalds wrote:
> On Thu, Nov 1, 2018 at 10:15 PM Dave Chinner wrote:
> >
> > Can you please pull update containing a rework of the VFS clone and
> > dedupe file range infrastructure from the tag listed below?
>
> I don't love the timing of this at
On Fri, Nov 02, 2018 at 09:35:23AM -0700, Linus Torvalds wrote:
> On Thu, Nov 1, 2018 at 10:15 PM Dave Chinner wrote:
> >
> > Can you please pull update containing a rework of the VFS clone and
> > dedupe file range infrastructure from the tag listed below?
>
> I don't love the timing of this at
On Sat, Nov 03, 2018 at 01:11:01AM +0200, Jarkko Sakkinen wrote:
> From: Kai Huang
>
> X86_FEATURE_SGX reflects whether or not the CPU supports Intel's
> Software Guard eXtensions (SGX).
>
> Signed-off-by: Kai Huang
This and all the other patches of which you're not the author, need to
have
On Sat, Nov 03, 2018 at 01:11:01AM +0200, Jarkko Sakkinen wrote:
> From: Kai Huang
>
> X86_FEATURE_SGX reflects whether or not the CPU supports Intel's
> Software Guard eXtensions (SGX).
>
> Signed-off-by: Kai Huang
This and all the other patches of which you're not the author, need to
have
On Fri, Nov 2, 2018 at 4:28 PM Jann Horn wrote:
>
> On Fri, Nov 2, 2018 at 11:04 PM Sean Christopherson
> wrote:
> > On Fri, Nov 02, 2018 at 08:02:23PM +0100, Jann Horn wrote:
> > > On Fri, Nov 2, 2018 at 7:27 PM Sean Christopherson
> > > wrote:
> > > > On Fri, Nov 02, 2018 at 10:48:38AM -0700,
On Fri, Nov 2, 2018 at 4:28 PM Jann Horn wrote:
>
> On Fri, Nov 2, 2018 at 11:04 PM Sean Christopherson
> wrote:
> > On Fri, Nov 02, 2018 at 08:02:23PM +0100, Jann Horn wrote:
> > > On Fri, Nov 2, 2018 at 7:27 PM Sean Christopherson
> > > wrote:
> > > > On Fri, Nov 02, 2018 at 10:48:38AM -0700,
This patch-set addresses some issues that were raised in a recent
correspondence and might affect the security and the correctness of code
patching. (Note that patching performance is not addressed by this
patch-set).
The main issue that the patches deal with is the fact that the fixmap
PTEs that
To prevent improper use of the PTEs that are used for text patching, we
want to use a temporary mm struct. We initailize it by copying the init
mm.
The address that will be used for patching is taken from the lower area
that is usually used for the task memory. Doing so prevents the need to
1 - 100 of 1600 matches
Mail list logo
