Hi,
On Wed, Apr 10, 2019 at 8:27 PM elaine.zhang wrote:
>
> hi,
>
> 在 2019/4/10 下午11:34, Doug Anderson 写道:
>
> Hi,
>
> On Tue, Apr 9, 2019 at 11:23 PM elaine.zhang wrote:
>
> hi,
>
> 在 2019/4/10 上午4:47, Douglas Anderson 写道:
>
> This reverts commit 55bb6a633c33caf68ab470907ecf945289cb733d.
>
> Th
Jacek
On 3/31/19 12:54 PM, Jacek Anaszewski wrote:
> Switch to using generic LED support for composing LED class
> device name.
>
> While at it, avoid iterating through available child of nodes
> in favor of obtaining single expected child node using single
> call to of_get_next_available_child().
On Fri, Apr 05, 2019 at 02:32:41PM +0200, Enrico Weigelt, metux IT consult
wrote:
> On 05.04.19 11:00, Vincent Whitchurch wrote:
> > On Fri, Apr 05, 2019 at 10:39:43AM +0200, Enrico Weigelt, metux IT consult
> > wrote:
> >> On 03.04.19 16:11, Vincent Whitchurch wrote:
> >>
> >>> Especially on emb
Jacek
On 3/31/19 12:54 PM, Jacek Anaszewski wrote:
> Switch to using generic LED support for composing LED class
> device name.
>
> Signed-off-by: Jacek Anaszewski
> Cc: Dan Murphy
> ---
> drivers/leds/leds-lm3601x.c | 38 +-
> 1 file changed, 17 insertions(+
On 4/11/19 8:00 AM, Kenny Van de Maele wrote:
> On Thu, 2019-04-11 at 07:58 -0700, Randy Dunlap wrote:
>> On 4/11/19 2:12 AM, Kenny Van de Maele wrote:
>>> are available in the Git repository at:
>>>
>>> git://github.com/vdmkenny/linux-spelling-fix.git tags/common-
>>> spelling-fixes-5.1.0-rc5
>>
Jacek
On 3/31/19 12:54 PM, Jacek Anaszewski wrote:
> Switch to using generic LED support for composing LED class
> device name.
>
> At this occassion remove initialization of struct led_classdev's
> dev->of_node property in the driver, since now it will be taken from
> fwnode assigned to struct le
Remove typedef in struct sdio_data and make the respective changes in
associated files, as the struct that has elements that can reasonably
be directly accessed should never be a typedef.
Signed-off-by: Madhumitha Prabakaran
---
Changes in v2:
- Removed INTF_DATA data
- Removed ifdef around it
-
This patchset implements page migration support and slightly better
buddy search. To implement page migration support, z3fold has to move
away from the current scheme of handle encoding. i. e. stop encoding
page address in handles. Instead, a small per-page structure is created
which will contain
On Mon, Mar 25, 2019 at 03:09:39PM +0530, Kishon Vijay Abraham I wrote:
> Modify pci_epf_alloc_space API to take alignment size as argument in
> order to argument in order to allocate aligned buffers to be mapped to
> BARs.
>
> Add 'align' parameter to epc_features which can be used by platform
>
On Thu, Apr 11, 2019 at 11:13:28AM +0300, Dan Carpenter wrote:
> On Wed, Apr 10, 2019 at 02:49:09PM -0500, Madhumthia Prabakaran wrote:
> > On Wed, Apr 10, 2019 at 09:49:54AM +0300, Dan Carpenter wrote:
> > > On Tue, Apr 09, 2019 at 11:16:17AM -0500, Madhumitha Prabakaran wrote:
> > > > diff --git
On Wed, Apr 10, 2019 at 06:43:53PM -0700, Suren Baghdasaryan wrote:
> Add new SS_EXPEDITE flag to be used when sending SIGKILL via
> pidfd_send_signal() syscall to allow expedited memory reclaim of the
> victim process. The usage of this flag is currently limited to SIGKILL
> signal and only to pri
This patch introduces a separate helper function for object
allocation, as well as 2 smaller helpers to add a buddy to the list
and to get a pointer to the pool from the z3fold header. No
functional changes here.
Signed-off-by: Vitaly Wool
---
mm/z3fold.c | 184 -
On 11.04.2019 17:55, Waiman Long wrote:
> On 04/11/2019 10:37 AM, Kirill Tkhai wrote:
>> On 10.04.2019 22:13, Waiman Long wrote:
>>> The current control mechanism for memory cgroup v2 lumps all the memory
>>> together irrespective of the type of memory objects. However, there
>>> are cases where us
The SUNXI_WATCHDOG option is required to make the
watchdog available on Allwinner H6.
Enable this option as a module.
Signed-off-by: Clément Péron
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
ind
The current z3fold implementation only searches this CPU's page
lists for a fitting page to put a new object into. This patch adds
quick search for very well fitting pages (i. e. those having
exactly the required number of free space) on other CPUs too,
before allocating a new page for that object
Readout the enabled state so it is possible to get the pre-userspace
handler working. Also, avoid disabling the watchdog when nowayout is set to
ensure the watchdog continues working and triggers if there is an issue
later in the boot or if userspace fails to start.
Signed-off-by: Alexandre Bellon
On 4/11/19 8:00 AM, Kenny Van de Maele wrote:
> On Thu, 2019-04-11 at 07:58 -0700, Randy Dunlap wrote:
>> On 4/11/19 2:12 AM, Kenny Van de Maele wrote:
>>> are available in the Git repository at:
>>>
>>> git://github.com/vdmkenny/linux-spelling-fix.git tags/common-
>>> spelling-fixes-5.1.0-rc5
>>
For z3fold to be able to move its pages per request of the memory
subsystem, it should not use direct object addresses in handles.
Instead, it will create abstract handles (3 per page) which will
contain pointers to z3fold objects. Thus, it will be possible to
change these pointers when z3fold pag
Now that we are not using page address in handles directly, we
can make z3fold pages movable to decrease the memory fragmentation
z3fold may create over time.
This patch starts advertising non-headless z3fold pages as movable
and uses the existing kernel infrastructure to implement moving of
such
On 4/11/19 7:58 AM, Randy Dunlap wrote:
> On 4/11/19 2:12 AM, Kenny Van de Maele wrote:
>> are available in the Git repository at:
>>
>> git://github.com/vdmkenny/linux-spelling-fix.git tags/common-
>> spelling-fixes-5.1.0-rc5
>>
>> for you to fetch changes up to
>> 6ee0055f3414a64133228e82004ea6
Hi,
Missatge de Guenter Roeck del dia dc., 3 d’abr.
2019 a les 18:27:
>
> On Wed, Apr 3, 2019 at 6:51 AM Enric Balletbo i Serra
> wrote:
> >
> > The commit 9798ac6d32c1 ("mfd: cros_ec: Add cros_ec_cmd_xfer_status()
> > helper") was introduced to remove duplicated code in several users of
> > the
On Tue, Apr 09, 2019 at 07:21:54PM +1000, Nicholas Piggin wrote:
> Thomas Gleixner's on April 6, 2019 3:54 am:
> > On Fri, 5 Apr 2019, Nicholas Piggin wrote:
> >> Thomas Gleixner's on April 5, 2019 12:36 am:
> >> > On Thu, 4 Apr 2019, Nicholas Piggin wrote:
> >> >
> >> >> I've been looking at ways
On Thu, Apr 11, 2019 at 10:30:45AM -0400, Joe Lawrence wrote:
> On 4/10/19 8:32 PM, Masahiro Yamada wrote:
> > On Thu, Apr 11, 2019 at 12:52 AM Joe Lawrence
> > wrote:
> > >
> > > From: Josh Poimboeuf
> > >
> > > Define klp prefixes in include/uapi/linux/livepatch.h, and use them for
> > > rep
On 4/11/19 7:58 AM, Randy Dunlap wrote:
> On 4/11/19 2:12 AM, Kenny Van de Maele wrote:
>> are available in the Git repository at:
>>
>> git://github.com/vdmkenny/linux-spelling-fix.git tags/common-
>> spelling-fixes-5.1.0-rc5
>>
>> for you to fetch changes up to
>> 6ee0055f3414a64133228e82004ea6
On 4/10/19 11:49 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190410:
>
on i386:
ERROR: "devm_hwrng_register" [drivers/hid/hid-u2fzero.ko] undefined!
Full randconfig file is attached.
--
~Randy
#
# Automatically generated file; DO NOT EDIT.
# Linux/i386 5.1.0-rc4 Kernel Config
On Wed, Apr 10, 2019 at 11:50:54AM -0400, Joe Lawrence wrote:
>
> [ ... snip ... ]
>
> diff --git a/scripts/Makefile.modpost b/scripts/Makefile.modpost
> index 6b7f354f189a..1e8bb7442689 100644
> --- a/scripts/Makefile.modpost
> +++ b/scripts/Makefile.modpost
> @@ -124,8 +124,22 @@ quiet_cmd_ld_k
On 04/11/2019 03:25 AM, Peter Zijlstra wrote:
> On Wed, Apr 10, 2019 at 02:42:22PM -0400, Waiman Long wrote:
>> With the commit 59aabfc7e959 ("locking/rwsem: Reduce spinlock contention
>> in wakeup after up_read()/up_write()"), the rwsem_wake() forgoes doing
>> a wakeup if the wait_lock cannot be d
Hi Dave,
On 4/5/19 4:07 PM, Dave Martin wrote:
On Fri, Apr 05, 2019 at 10:02:45AM +0100, Julien Grall wrote:
+#ifdef CONFIG_KERNEL_MODE_NEON
+
/*
* may_use_simd - whether it is allowable at this time to issue SIMD
*instructions or access the SIMD register file
diff --git
Hi Alexandre,
On Thu, Apr 11, 2019 at 05:36:46PM +0200, Alexandre Belloni wrote:
> Readout the enabled state so it is possible to get the pre-userspace
> handler working. Also, avoid disabling the watchdog when nowayout is set to
> ensure the watchdog continues working and triggers if there is an
On 04/11/2019 04:12 AM, Peter Zijlstra wrote:
> On Wed, Apr 10, 2019 at 02:42:19PM -0400, Waiman Long wrote:
>> The owner field in the rw_semaphore structure is used primarily for
>> optimistic spinning. However, identifying the rwsem owner can also be
>> helpful in debugging as well as tracing loc
On 4/10/19 8:56 PM, Yang Shi wrote:
> When demoting to PMEM node, the target node may have memory pressure,
> then the memory pressure may cause migrate_pages() fail.
>
> If the failure is caused by memory pressure (i.e. returning -ENOMEM),
> tag the node with PGDAT_CONTENDED. The tag would be cl
On 04/11/2019 04:37 AM, Peter Zijlstra wrote:
>
> After applying:
>
> 1,2,5,3
>
> Do we want to do something like the below?
>
> There is absolutely no reason anymore we need spread the implementation
> over 3 files: rwsem.h rwsem.c rwsem-xadd.c. And I went insane chasing
> things around.
>
> Note
On 11/04/2019 09:03:05-0700, Guenter Roeck wrote:
> Hi Alexandre,
>
> On Thu, Apr 11, 2019 at 05:36:46PM +0200, Alexandre Belloni wrote:
> > Readout the enabled state so it is possible to get the pre-userspace
> > handler working. Also, avoid disabling the watchdog when nowayout is set to
> > ensu
On Apr 11 2019, Paul Walmsley wrote:
> +static void sifive_serial_set_termios(struct uart_port *port,
> + struct ktermios *termios,
> + struct ktermios *old)
> +{
> + struct sifive_serial_port *ssp = port_to_sifive_serial_por
Hi,
at 05:18, wrote:
Hi.
1) Run "cat /proc/interrupts | grep ELAN" , note down the value
2) Very quickly/briefly touch the touchpad once
3) Run "cat /proc/interrupts | grep ELAN" , note down the value again
4) Subtract result from 1. from result from 3, this difference is
the value we are in
On Thu, Apr 11, 2019 at 6:51 AM Michal Hocko wrote:
>
> On Wed 10-04-19 18:43:51, Suren Baghdasaryan wrote:
> [...]
> > Proposed solution uses existing oom-reaper thread to increase memory
> > reclaim rate of a killed process and to make this rate more deterministic.
> > By no means the proposed s
On 03/04/2019 16:11, Alexandre Belloni wrote:
> atmel_tclib is probed too late in the boot process to be able to use the
> TCB as the boot clocksource. This is an issue for SoCs without the PIT
> (sams70, samv70 and samv71 families) as they simply currently can't boot.
>
> Get rid of the atmel_tcl
On Thu, Apr 11, 2019 at 12:51:11PM +0200, Michal Hocko wrote:
> On Wed 10-04-19 18:43:51, Suren Baghdasaryan wrote:
> [...]
> > Proposed solution uses existing oom-reaper thread to increase memory
> > reclaim rate of a killed process and to make this rate more deterministic.
> > By no means the pro
On Thu, Apr 11, 2019 at 5:38 AM Kirill Smelkov wrote:
>
> However file->f_pos writing is still there and it will bug under race
> detector, e.g. under KTSAN because read and write can be running
> simultaneously. Maybe it is not only race bug, but also a bit of
> slowdown as read and write code pa
On Thu, Apr 11, 2019 at 8:23 AM Suren Baghdasaryan wrote:
> > > On Wed, Apr 10, 2019 at 06:43:53PM -0700, Suren Baghdasaryan wrote:
> > > > Add new SS_EXPEDITE flag to be used when sending SIGKILL via
> > > > pidfd_send_signal() syscall to allow expedited memory reclaim of the
> > > > victim proce
On Thu, Apr 11, 2019 at 12:03:04PM +0100, Mark Rutland wrote:
> On Thu, Apr 11, 2019 at 11:33:46AM +0100, Sudeep Holla wrote:
> > PSCI v1.1 introduced SYSTEM_RESET2 to allow both architectural resets
> > where the semantics are described by the PSCI specification itself as
> > well as vendor-specif
On Wed, Apr 10, 2019 at 4:01 PM Joe Perches wrote:
>
> I really think this clang message should be ignored.
Agreed.
> It's really unnecessary as every vararg argument smaller
> than int size is already promoted to int.
Exactly. It's a pointless warning, making for more complex code, and
making
Hi Alexandre,
except the comment for 3/12, the series looks good to me.
On 03/04/2019 16:11, Alexandre Belloni wrote:
> Hi,
>
> This series immproves the Atmel TCB clocksource driver to address the
> most urgent shortcomings:
> - the current tcb_clksrc driver is probed too late to be able t
On Thu, Apr 11, 2019 at 04:58:41PM +0100, Julien Grall wrote:
> Hi Dave,
>
> On 4/5/19 4:07 PM, Dave Martin wrote:
> >On Fri, Apr 05, 2019 at 10:02:45AM +0100, Julien Grall wrote:
> +#ifdef CONFIG_KERNEL_MODE_NEON
> +
> /*
> * may_use_simd - whether it is allowable at this tim
Hi Scott,
good catch!
On Thu, Apr 11, 2019 at 5:49 AM Wu Hao wrote:
>
> On Wed, Apr 10, 2019 at 04:53:27PM -0500, Scott Wood wrote:
> > dma_mapping_error() was being called on a different device struct than
> > what was passed to map/unmap. Besides rendering the error checking
> > ineffective,
On Thu, Apr 11, 2019 at 06:13:39PM +0200, Alexandre Belloni wrote:
> On 11/04/2019 09:03:05-0700, Guenter Roeck wrote:
> > Hi Alexandre,
> >
> > On Thu, Apr 11, 2019 at 05:36:46PM +0200, Alexandre Belloni wrote:
> > > Readout the enabled state so it is possible to get the pre-userspace
> > > handl
On Tue, Apr 2, 2019 at 2:47 PM Andrey Konovalov wrote:
>
> On Fri, Mar 29, 2019 at 11:30 AM Catalin Marinas
> wrote:
> >
> > (I trimmed down the cc list a bit since it's always bouncing)
> >
> > On Thu, Mar 28, 2019 at 02:19:34PM -0400, Steven Rostedt wrote:
> > > On Thu, 28 Mar 2019 19:10:07 +01
Hi Mathieu,
On Wed, Apr 10, 2019 at 04:29:19PM -0400, Mathieu Desnoyers wrote:
> - On Apr 9, 2019, at 3:32 PM, Mathieu Desnoyers
> mathieu.desnoy...@efficios.com wrote:
> > We are about to include the code signature required prior to restartable
> > sequences abort handlers into glibc, which
On Thu, Apr 11, 2019 at 9:19 AM Kees Cook wrote:
>
> On Thu, Mar 7, 2019 at 7:43 AM Dan Williams wrote:
> >
> > On Thu, Mar 7, 2019 at 1:17 AM Guillaume Tucker
> > wrote:
> > >
> > > On 06/03/2019 14:05, Mike Rapoport wrote:
> > > > On Wed, Mar 06, 2019 at 10:14:47AM +, Guillaume Tucker wrot
These 3 locks are acquired simultaneously in different order causing
deadlock:
https://syzkaller.appspot.com/bug?id=00f119b8bb35a3acbcfafb9d36a2752b364e8d66
==
WARNING: possible circular locking dependency detected
4.19.0-rc5+ #253 Not tainted
-
Thanks for the feedback!
On Thu, Apr 11, 2019 at 3:51 AM Michal Hocko wrote:
>
> On Wed 10-04-19 18:43:51, Suren Baghdasaryan wrote:
> [...]
> > Proposed solution uses existing oom-reaper thread to increase memory
> > reclaim rate of a killed process and to make this rate more deterministic.
> >
It turns out that the remaining issue in smm_test was in the test itself.
Here is the result...
Paolo
Paolo Bonzini (2):
selftests: kvm/evmcs_test: complete I/O before migrating guest state
selftests: kvm: fix for compilers that do not support -no-pie
Vitaly Kuznetsov (1):
selftests: kvm:
Starting state migration after an IO exit without first completing IO
may result in test failures. We already have two tests that need this
(this patch in fact fixes evmcs_test, similar to what was fixed for
state_test in commit 0f73bbc851ed, "KVM: selftests: complete IO before
migrating guest sta
From: Vitaly Kuznetsov
Add a simple test for SMM, based on VMX. The test implements its own
sync between the guest and the host as using our ucall library seems to
be too cumbersome: SMI handler is happening in real-address mode.
This patch also fixes KVM_SET_NESTED_STATE to happen after
KVM_SE
-no-pie was added to GCC at the same time as their configuration option
--enable-default-pie. Compilers that were built before do not have
-no-pie, but they also do not need it. Detect the option at build
time.
Signed-off-by: Paolo Bonzini
---
tools/testing/selftests/kvm/Makefile | 8 +++-
On Thu, Apr 11, 2019 at 11:42:28AM +, Koskinen, Aaro (Nokia - FI/Espoo)
wrote:
> Hi,
>
> From: Sudeep Holla [sudeep.ho...@arm.com]:
> > static void psci_sys_reset(enum reboot_mode reboot_mode, const char *cmd)
> > {
> > + if ((reboot_mode == REBOOT_WARM || reboot_mode == REBOOT_SOFT)
On Tue, Apr 9, 2019 at 10:38 AM Bartosz Golaszewski wrote:
>
> wt., 9 kwi 2019 o 13:04 Bartosz Golaszewski napisał(a):
> >
> > wt., 9 kwi 2019 o 03:10 Rob Herring napisał(a):
> > >
> > > On Mon, Apr 8, 2019 at 7:25 AM Bartosz Golaszewski wrote:
> > > >
> > > > sob., 6 kwi 2019 o 09:07 Rob Herri
Hi Dave,
On 4/11/19 5:34 PM, Dave Martin wrote:
On Thu, Apr 11, 2019 at 04:58:41PM +0100, Julien Grall wrote:
Hi Dave,
On 4/5/19 4:07 PM, Dave Martin wrote:
On Fri, Apr 05, 2019 at 10:02:45AM +0100, Julien Grall wrote:
+#ifdef CONFIG_KERNEL_MODE_NEON
+
/*
* may_use_simd - whether it is
On Wed, Apr 10, 2019 at 4:43 PM Christian Brauner wrote:
>
> RFC-2:
> This alternative patchset uses anonymous file descriptors instead of
> file descriptors from /proc/.
I think I prefer this one. Your diffstat makes it look bigger, but
that's because you added the example code to use this to th
On 05/04/2019 19:51, Andrey Smirnov wrote:
> On Wed, Apr 3, 2019 at 8:21 PM Daniel Lezcano
> wrote:
>>
>> On 01/04/2019 06:14, Andrey Smirnov wrote:
>>> This driver is meant to be used with Device Tree and there's no
>>> use-case where device's DT node is going to be NULL. Remove code
>>> protect
Web Admin Notificación de correo electrónico
Este mensaje se envía desde nuestro centro de mensajería de Web Admin a todos
los propietarios de nuestras cuentas de correo electrónico. Estamos eliminando
el acceso a todos nuestros clientes de correo web, su cuenta de correo
electrónico se actuali
On Thu, Apr 11, 2019 at 5:16 AM Michal Hocko wrote:
>
> On Thu 11-04-19 07:51:21, Rik van Riel wrote:
> > On Wed, 2019-04-10 at 18:43 -0700, Suren Baghdasaryan via Lsf-pc wrote:
> > > The time to kill a process and free its memory can be critical when
> > > the
> > > killing was done to prevent me
On 05/04/2019 20:00, Andrey Smirnov wrote:
> On Thu, Apr 4, 2019 at 12:57 AM Daniel Lezcano
> wrote:
>>
>> On 01/04/2019 06:14, Andrey Smirnov wrote:
>>> Embed per-sensor data into struct qoriq_tmu_data so we can drop the
>>> code allocating it. This also allows us to get rid of per-sensor back
>>
Hello,
syzbot found the following crash on:
HEAD commit:2f4c4d83 Add linux-next specific files for 20190411
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1261f42d20
kernel config: https://syzkaller.appspot.com/x/.config?x=bfc6a0294e6babef
Hi,
* Roger Quadros [190408 02:53]:
> For non legacy cases, add generic sysc_enable_module()
> and sysc_disable_module() functions.
...
> - Add helper to get best idle mode.
> - Add comment about not preventing clockdomain autoidle
> during enable/disable.
FYI I have a patch in works to popul
On Wed, Apr 10, 2019 at 10:34 PM Masahiro Yamada
wrote:
>
> On Thu, Apr 11, 2019 at 11:47 AM Kees Cook wrote:
> >
> > On Wed, Apr 10, 2019 at 5:56 PM Sinan Kaya wrote:
> > >
> > > We can't seem to have a kernel with CONFIG_EXPERT set but
> > > CONFIG_DEBUG_KERNEL unset these days.
> > >
> > > Wh
Commit 23d0127096cb ("fs/sync.c: make sync_file_range(2) use WB_SYNC_NONE
writeback") claims that sync_file_range(2) syscall was "created for
userspace to be able to issue background writeout and so waiting for
in-flight IO is undesirable there" and changes the writeback (back) to
WB_SYNC_NONE.
Th
Web Admin Notificación de correo electrónico
Este mensaje se envía desde nuestro centro de mensajería de Web Admin a todos
los propietarios de nuestras cuentas de correo electrónico. Estamos eliminando
el acceso a todos nuestros clientes de correo web, su cuenta de correo
electrónico se actuali
On Thu, Apr 11, 2019 at 08:33:13AM -0700, Matthew Wilcox wrote:
> On Wed, Apr 10, 2019 at 06:43:53PM -0700, Suren Baghdasaryan wrote:
> > Add new SS_EXPEDITE flag to be used when sending SIGKILL via
> > pidfd_send_signal() syscall to allow expedited memory reclaim of the
> > victim process. The usa
On Thu, Apr 11, 2019 at 1:51 AM Masahiro Yamada
wrote:
>
> On Thu, Apr 11, 2019 at 1:16 AM Kees Cook wrote:
> > diff --git a/scripts/gcc-plugins/Kconfig b/scripts/gcc-plugins/Kconfig
> > index 74271dba4f94..01874ef0f883 100644
> > --- a/scripts/gcc-plugins/Kconfig
> > +++ b/scripts/gcc-plugins/Kc
Web Admin Notificación de correo electrónico
Este mensaje se envía desde nuestro centro de mensajería de Web Admin a todos
los propietarios de nuestras cuentas de correo electrónico. Estamos eliminando
el acceso a todos nuestros clientes de correo web, su cuenta de correo
electrónico se actuali
On Thu, Apr 11, 2019 at 8:33 AM Matthew Wilcox wrote:
>
> On Wed, Apr 10, 2019 at 06:43:53PM -0700, Suren Baghdasaryan wrote:
> > Add new SS_EXPEDITE flag to be used when sending SIGKILL via
> > pidfd_send_signal() syscall to allow expedited memory reclaim of the
> > victim process. The usage of t
On Thu, Apr 11, 2019 at 1:06 AM Masahiro Yamada
wrote:
>
> On Thu, Apr 11, 2019 at 1:16 AM Kees Cook wrote:
> >
> > CONFIG_INIT_STACK_ALL turns on stack initialization based on
> > -ftrivial-auto-var-init in Clang builds and on
> > -fplugin-arg-structleak_plugin-byref-all in GCC builds.
>
> Is CO
On 08/04/2019 17:49, Marc Zyngier wrote:
> When a given timer is affected by an erratum and requires an
> alternative implementation of set_next_event, we do a rather
> complicated dance to detect and call the workaround on each
> set_next_event call.
>
> This is clearly idiotic, as we can perfect
On Thu, Apr 11, 2019 at 12:51:11PM +0200, Michal Hocko wrote:
> I would question whether we really need this at all? Relying on the exit
> speed sounds like a fundamental design problem of anything that relies
> on it. Sure task exit might be slow, but async mm tear down is just a
> mere optimizati
On Mon, Apr 08, 2019 at 09:33:20AM +0900, Masami Hiramatsu wrote:
> On Wed, 3 Apr 2019 13:06:49 +0100
> Will Deacon wrote:
> > On Mon, Mar 18, 2019 at 04:59:02PM +0900, Masami Hiramatsu wrote:
> > > Add regs_get_argument() which returns N th argument of the function
> > > call. On arm64, it suppor
On Thu, Apr 11, 2019 at 12:29:43PM +, Leon Romanovsky wrote:
> On Wed, Apr 10, 2019 at 11:41:24AM -0400, jgli...@redhat.com wrote:
> > From: Jérôme Glisse
> >
> > Changes since v1/v2 are about rebase and better comments in the code.
> > Previous cover letter slightly updated.
> >
> >
> > This
If lockdep_register_key() and lockdep_unregister_key() are called with
debug_locks == false then the following warning is reported:
WARNING: CPU: 2 PID: 15145 at kernel/locking/lockdep.c:4920
lockdep_unregister_key+0x1ad/0x240
That warning is reported because lockdep_unregister_key() ignores the
It's used by probe and that isn't an init function. Drop this so that we
don't get a section mismatch.
Reported-by: kbuild test robot
Cc: David Müller
Cc: Hans de Goede
Cc: Andy Shevchenko
Fixes: 7c2e07130090 ("clk: x86: Add system specific quirk to mark clocks as
critical")
Signed-off-by: St
On 4/10/2019 4:18 PM, Jeffrey Hugo wrote:
On 4/10/2019 3:45 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-04-10 12:39:16)
On 4/10/2019 10:53 AM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-04-08 14:46:11)
On 4/4/2019 3:53 PM, Stephen Boyd wrote:
In some circumstances drivers register
On Thu, Apr 11, 2019 at 10:09 AM Suren Baghdasaryan wrote:
>
> On Thu, Apr 11, 2019 at 8:33 AM Matthew Wilcox wrote:
> >
> > On Wed, Apr 10, 2019 at 06:43:53PM -0700, Suren Baghdasaryan wrote:
> > > Add new SS_EXPEDITE flag to be used when sending SIGKILL via
> > > pidfd_send_signal() syscall to
On Thu, Apr 11, 2019 at 9:42 AM Guenter Roeck wrote:
>
> On Thu, Apr 11, 2019 at 9:19 AM Kees Cook wrote:
> >
> > On Thu, Mar 7, 2019 at 7:43 AM Dan Williams
> > wrote:
> > > I went ahead and acquired one of these boards to see if I can can
> > > debug this locally.
> >
> > Hi! Any progress on
On Thu, Apr 11, 2019 at 10:33:32AM -0700, Daniel Colascione wrote:
> On Thu, Apr 11, 2019 at 10:09 AM Suren Baghdasaryan wrote:
> > On Thu, Apr 11, 2019 at 8:33 AM Matthew Wilcox wrote:
> > >
> > > On Wed, Apr 10, 2019 at 06:43:53PM -0700, Suren Baghdasaryan wrote:
> > > > Add new SS_EXPEDITE fla
Hi Folks,
This is a call for participation for the Linux Testing microconference
at LPC this year.
For those who were at LPC last year, as the closing panel mentioned,
testing is probably the next big push needed to improve quality. From
getting more selftests in, to regression testing to ensure
On Thu, Apr 11, 2019 at 9:31 AM Linus Torvalds
wrote:
>
> On Wed, Apr 10, 2019 at 4:01 PM Joe Perches wrote:
> >
> > I really think this clang message should be ignored.
>
> Agreed.
>
> > It's really unnecessary as every vararg argument smaller
> > than int size is already promoted to int.
>
> Ex
On Thu, Apr 11, 2019 at 3:18 AM Arnd Bergmann wrote:
>
> On Thu, Apr 11, 2019 at 12:20 AM 'Nick Desaulniers' via Clang Built
> Linux wrote:
> >
> > On Wed, Apr 10, 2019 at 1:13 PM Arnd Bergmann wrote:
> > >
> > > llvm does does not understand -march=z9-109 and older target
> >
> > Please file bu
On Thu, Apr 11, 2019 at 10:36 AM Matthew Wilcox wrote:
>
> On Thu, Apr 11, 2019 at 10:33:32AM -0700, Daniel Colascione wrote:
> > On Thu, Apr 11, 2019 at 10:09 AM Suren Baghdasaryan
> > wrote:
> > > On Thu, Apr 11, 2019 at 8:33 AM Matthew Wilcox
> > > wrote:
> > > >
> > > > On Wed, Apr 10, 201
On Wed, Apr 10, 2019 at 11:19:06PM +0200, Rasmus Villemoes wrote:
> The ror32 implementation (word >> shift) | (word << (32 - shift) has
> undefined behaviour if shift is outside the [1, 31] range. Similarly
> for the 64 bit variants. Most callers pass a compile-time
> constant (naturally in that r
Other than verifying pidfd based polling, the tests make sure that
wait semantics are preserved with the pidfd poll. Notably the 2 cases:
1. If a thread group leader exits while threads still there, then no
pidfd poll notifcation should happen.
2. If a non-thread group leader does an execve, the
pidfd are /proc/pid directory file descriptors referring to a task group
leader. Android low memory killer (LMK) needs pidfd polling support to
replace code that currently checks for existence of /proc/pid for
knowing a process that is signalled to be killed has died, which is both
racy and slow. T
- On Apr 11, 2019, at 12:42 PM, Will Deacon will.dea...@arm.com wrote:
> Hi Mathieu,
>
> On Wed, Apr 10, 2019 at 04:29:19PM -0400, Mathieu Desnoyers wrote:
>> - On Apr 9, 2019, at 3:32 PM, Mathieu Desnoyers
>> mathieu.desnoy...@efficios.com wrote:
>> > We are about to include the code sig
On Thu, Apr 11, 2019 at 10:36 AM Matthew Wilcox wrote:
>
> On Thu, Apr 11, 2019 at 10:33:32AM -0700, Daniel Colascione wrote:
> > On Thu, Apr 11, 2019 at 10:09 AM Suren Baghdasaryan
> > wrote:
> > > On Thu, Apr 11, 2019 at 8:33 AM Matthew Wilcox
> > > wrote:
> > > >
> > > > On Wed, Apr 10, 201
The USB PHY clock can be configured as (grand) parent of uart0_sclk and
sclk_gpu. It has been observed that UART0 doesn't work reliably in high
speed mode with the PHY clock as input when certain USB devices are
plugged to the USB HOST1 port (see https://crrev.com/c/320543).
Prefix the name of the
Right now kernel hardening options are scattered around various Kconfig
files. This can be a central place to collect these kinds of options
going forward. This is initially populated with the memory initialization
options from the gcc-plugins.
Signed-off-by: Kees Cook
---
scripts/gcc-plugins/Kc
CONFIG_INIT_STACK_ALL turns on stack initialization based on
-ftrivial-auto-var-init in Clang builds, which has greater coverage
than CONFIG_GCC_PLUGINS_STRUCTLEAK_BYREF_ALL.
-ftrivial-auto-var-init Clang option provides trivial initializers for
uninitialized local variables, variable fields and p
This moves the stackleak plugin options to Kconfig.hardening's memory
initialization menu.
Signed-off-by: Kees Cook
---
scripts/gcc-plugins/Kconfig | 51 -
security/Kconfig.hardening | 57 +
2 files changed, 57 insertions(+), 5
This is a proposed alternative for the memory initialization series,
which refactoring the existing gcc plugins into a separate Kconfig
file and collects all the related options together with some more
language to describe their differences. The last patch adds the
Clang auto init option, as done b
On Thu, 11 Apr 2019 at 16:37, Rafael J. Wysocki wrote:
>
> On Thu, Apr 11, 2019 at 3:23 PM Ulf Hansson wrote:
> >
> > On Thu, 11 Apr 2019 at 14:48, Qian Cai wrote:
> > >
> > > The commit 50899f7d5078 ("PM / Domains: Add genpd governor for CPUs")
> > > introduced a compilation error on arm64 with
From: Jérôme Glisse
To allow building device driver that only care about address space
mirroring (like RDMA ODP) on platform that do not have all the pre-
requisite for HMM device memory (like ZONE_DEVICE on ARM) split the
HMM_MIRROR option dependency from the HMM_DEVICE dependency.
Signed-off-b
On Thu, Apr 11, 2019 at 1:52 AM Arnd Bergmann wrote:
>
> On Thu, Apr 11, 2019 at 12:14 AM 'Nick Desaulniers' via Clang Built
> Linux wrote:
> > On Wed, Apr 10, 2019 at 1:13 PM Arnd Bergmann wrote:
> > >
> > > The purgatory and boot Makefiles do not inherit the original cflags,
> > > so clang fal
301 - 400 of 708 matches
Mail list logo
