Re: [PATCH v20 00/28] Intel SGX1 support

On 2019-04-19 13:46, Jethro Beekman wrote: > On 2019-04-19 13:39, Thomas Gleixner wrote: >> On Fri, 19 Apr 2019, Jethro Beekman wrote: >> >>> On 2019-04-19 08:27, Andy Lutomirski wrote: There are many, many Linux systems that enforce a policy that *all* executable text needs to come

[PATCH bpf-next v3 5/5] selftests: bpf: test writable buffers in raw tps

This tests that: * a BPF_PROG_TYPE_RAW_TRACEPOINT_WRITABLE cannot be attached if it uses either: * a variable offset to the tracepoint buffer, or * an offset beyond the size of the tracepoint buffer * a tracer can modify the buffer provided when attached to a writable

Re: [PATCH v2] PCI/LINK: bw_notification: Do not leave interrupt handler NULL

On Mon, 25 Mar 2019 17:25:02 -0500 Bjorn Helgaas wrote: > On Fri, Mar 22, 2019 at 07:36:51PM -0500, Alexandru Gagniuc wrote: > > A threaded IRQ with a NULL handler does not work with level-triggered > > interrupts. request_threaded_irq() will return an error: > > > > genirq: Threaded irq

[PATCH] Staging: mt7621-mmc: Cleanup in msdc_app_cmd()

Remove unwanted variable and replace the respective return type. Issue suggested by Coccinelle. Signed-off-by: Madhumitha Prabakaran --- drivers/staging/mt7621-mmc/sd.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/staging/mt7621-mmc/sd.c

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 10:01:00PM +0200, Christian Brauner wrote: > On Fri, Apr 19, 2019 at 03:49:02PM -0400, Joel Fernandes wrote: > > On Fri, Apr 19, 2019 at 09:18:59PM +0200, Christian Brauner wrote: > > > On Fri, Apr 19, 2019 at 03:02:47PM -0400, Joel Fernandes wrote: > > > > On Thu, Apr 18,

Re: [tip:core/rseq] rseq/selftests/x86: Work around bogus gcc-8 optimisation

- On Apr 19, 2019, at 2:53 PM, Linus Torvalds torva...@linux-foundation.org wrote: > On Fri, Apr 19, 2019 at 11:46 AM tip-bot for Mathieu Desnoyers > wrote: >> >> rseq/selftests/x86: Work around bogus gcc-8 optimisation >> >> At least the following versions of gcc-8: >> >> - gcc version

Re: [PATCH v5 0/2] tty: serial: add DT bindings and serial driver for the SiFive FU540 UART

On Fri, 19 Apr 2019, Kevin Hilman wrote: > Looks like Paul has so far only tested this with BBL + FSBL, so I think > I'll wait to hear from him how that setup might be different from using > OpenSBI + u-boot. I'd recommend testing the DT patches with BBL and the open-source FSBL. That's the

Re: [PATCH] memcg: refill_stock for kmem uncharging too

On Fri, Apr 19, 2019 at 1:07 PM Roman Gushchin wrote: > > On Thu, Apr 18, 2019 at 02:42:24PM -0700, Shakeel Butt wrote: > > The commit 475d0487a2ad ("mm: memcontrol: use per-cpu stocks for socket > > memory uncharging") added refill_stock() for skmem uncharging path to > > optimize workloads

Re: [PATCH v20 00/28] Intel SGX1 support

> On Apr 19, 2019, at 1:54 PM, Jethro Beekman wrote: > >> On 2019-04-19 13:50, Thomas Gleixner wrote: >>> On Fri, 19 Apr 2019, Jethro Beekman wrote: On 2019-04-19 13:39, Thomas Gleixner wrote: > On Fri, 19 Apr 2019, Jethro Beekman wrote: > >> On 2019-04-19 08:27, Andy

Re: [PATCH] ARM: dts: exynos: add CCI-400 PMU nodes support to Exynos542x SoCs

On 2019-04-19 6:53 pm, Willy Wolff wrote: Hi, This patch can be dropped, as it needs more work. In fact, the interrupts seems to be wrong. The interrupts suggested by Anand Moon gave the same following results. export CCI_DEV=CCI_400 export OMP_NUM_THREADS=2 sudo --preserve-env ./perf stat -a

Re: [PATCH v20 00/28] Intel SGX1 support

Jethro Beekman | Fortanix On 2019-04-19 14:15, Andy Lutomirski wrote: > > > > >> On Apr 19, 2019, at 1:54 PM, Jethro Beekman wrote: >> >>> On 2019-04-19 13:50, Thomas Gleixner wrote: On Fri, 19 Apr 2019, Jethro Beekman wrote: > On 2019-04-19 13:39, Thomas Gleixner wrote: >> On

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 10:57:11PM +0200, Christian Brauner wrote: > On Fri, Apr 19, 2019 at 10:34 PM Daniel Colascione wrote: > > > > On Fri, Apr 19, 2019 at 12:49 PM Joel Fernandes > > wrote: > > > > > > On Fri, Apr 19, 2019 at 09:18:59PM +0200, Christian Brauner wrote: > > > > On Fri, Apr

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 1:57 PM Christian Brauner wrote: > > On Fri, Apr 19, 2019 at 10:34 PM Daniel Colascione wrote: > > > > On Fri, Apr 19, 2019 at 12:49 PM Joel Fernandes > > wrote: > > > > > > On Fri, Apr 19, 2019 at 09:18:59PM +0200, Christian Brauner wrote: > > > > On Fri, Apr 19, 2019

[PATCH] Staging: vc04_services: Cleanup in ctrl_set_bitrate()

Remove unnecessary variable and replace return type. Issue suggested by Coccinelle. Signed-off-by: Madhumitha Prabakaran --- drivers/staging/vc04_services/bcm2835-camera/controls.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 2:20 PM Joel Fernandes wrote: > > On Fri, Apr 19, 2019 at 10:57:11PM +0200, Christian Brauner wrote: > > On Fri, Apr 19, 2019 at 10:34 PM Daniel Colascione > > wrote: > > > > > > On Fri, Apr 19, 2019 at 12:49 PM Joel Fernandes > > > wrote: > > > > > > > > On Fri, Apr

Re: [PATCH v2] PCI/LINK: bw_notification: Do not leave interrupt handler NULL

On Fri, Apr 19, 2019 at 03:08:27PM -0600, Alex Williamson wrote: > On Mon, 25 Mar 2019 17:25:02 -0500, Bjorn Helgaas wrote: > > On Fri, Mar 22, 2019 at 07:36:51PM -0500, Alexandru Gagniuc wrote: > > > A threaded IRQ with a NULL handler does not work with level-triggered > > > interrupts.

Re: [PATCH V2] staging: vc04_services: handle kzalloc failure

Am 19.04.19 um 01:31 schrieb Nicholas Mc Guire: > The kzalloc here was being used without checking the return - if the > kzalloc fails return VCHIQ_ERROR. The call-site of > vchiq_platform_init_state() vchiq_init_state() was not responding > to an allocation failure so checks for !=

Re: [PATCH v2 3/9] x86/paravirt: Replace paravirt patches with data

On Fri, 29 Mar 2019, Andi Kleen wrote: > For LTO all top level assembler statements need to be global because > LTO might put it into a different assembler file than the referencing > C code. > > To avoid making all the paravirt patch snippets global replace them > with data containing the patch

[GIT PULL] percpu changes for v5.1-rc6

Hi Linus, This stops printing the base address of percpu memory on initialization. Thanks, Dennis The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b: Linux 5.1-rc1 (2019-03-17 14:22:26 -0700) are available in the Git repository at:

Re: [PATCH v20 00/28] Intel SGX1 support

> On Apr 19, 2019, at 2:19 PM, Jethro Beekman wrote: > >> . >> >> If we start enforcing equivalent rules on SGX, then the current API will >> simply not allow enclaves to be loaded — no matter how you slice it, loading >> an enclave with the current API is indistinguishable from making

Re: [PATCH] PCI: keystone: Fix build error while only CONFIG_PCI_KEYSTONE is set

On 2019/4/19 21:31, Bjorn Helgaas wrote: > On Fri, Apr 19, 2019 at 10:58:55AM +0800, Yue Haibing wrote: >> From: YueHaibing >> >> During randconfig builds, I occasionally run into an invalid configuration >> >> drivers/pci/controller/dwc/pci-keystone.o: In function `ks_pcie_link_up': >>

[PATCH] Staging: rtlwifi: Replace return type

Replace return type and remove the respective assignment. Issue found by Coccinelle. Signed-off-by: Madhumitha Prabakaran --- drivers/staging/rtlwifi/core.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/staging/rtlwifi/core.c b/drivers/staging/rtlwifi/core.c

Re: [PATCH v20 00/28] Intel SGX1 support

On Fri, 19 Apr 2019, Jethro Beekman wrote: > On 2019-04-19 14:15, Andy Lutomirski wrote: > > With plain mmap() + mprotect(), the LSM will prevent you from making > > memory that *was* writable executable. This is by design and SELinux > > supports it. I don’t remember the name of the associated

Re: [PATCH v20 00/28] Intel SGX1 support

On 2019-04-19 14:31, Andy Lutomirski wrote: > I do think we need to follow LSM rules. But my bigger point is that there > are policies that don’t allow JIT at all. I think we should arrange the SGX > API so it’s still usable when such a policy is in effect. I don't think we need to arrange

Re: [PATCH v20 00/28] Intel SGX1 support

On Fri, 19 Apr 2019, Jethro Beekman wrote: > On 2019-04-19 14:31, Andy Lutomirski wrote: > > I do think we need to follow LSM rules. But my bigger point is that > > there are policies that don’t allow JIT at all. I think we should > > arrange the SGX API so it’s still usable when such a policy is

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 02:24:09PM -0700, Daniel Colascione wrote: > On Fri, Apr 19, 2019 at 2:20 PM Joel Fernandes wrote: > > > > On Fri, Apr 19, 2019 at 10:57:11PM +0200, Christian Brauner wrote: > > > On Fri, Apr 19, 2019 at 10:34 PM Daniel Colascione > > > wrote: > > > > > > > > On Fri, Apr

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione wrote: > > On Fri, Apr 19, 2019 at 1:57 PM Christian Brauner > wrote: > > > > On Fri, Apr 19, 2019 at 10:34 PM Daniel Colascione > > wrote: > > > > > > On Fri, Apr 19, 2019 at 12:49 PM Joel Fernandes > > > wrote: > > > > > > > > On Fri, Apr

Re: [PATCH] Staging: vc04_services: Cleanup in ctrl_set_bitrate()

Hi Madhumitha, Am 19.04.19 um 23:23 schrieb Madhumitha Prabakaran: > Remove unnecessary variable and replace return type. > > Issue suggested by Coccinelle. > > Signed-off-by: Madhumitha Prabakaran > --- > drivers/staging/vc04_services/bcm2835-camera/controls.c | 7 +-- > 1 file changed, 1

mmotm 2019-04-19-14-53 uploaded

The mm-of-the-moment snapshot 2019-04-19-14-53 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

Re: [PATCH v20 00/28] Intel SGX1 support

On 2019-04-19 14:34, Thomas Gleixner wrote: > And how so? You create writeable AND executable memory. That's a nono and > you can argue in circles, that's not going to change with any of your > proposed changes. On 2019-04-19 14:38, Thomas Gleixner wrote: > You are working around LSM nothing else

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 11:20 PM Joel Fernandes wrote: > > On Fri, Apr 19, 2019 at 10:57:11PM +0200, Christian Brauner wrote: > > On Fri, Apr 19, 2019 at 10:34 PM Daniel Colascione > > wrote: > > > > > > On Fri, Apr 19, 2019 at 12:49 PM Joel Fernandes > > > wrote: > > > > > > > > On Fri, Apr

Re: [PATCH v1 2/3] PCI / ACPI: Remove the need for 'struct hotplug_params'

On Fri, Apr 19, 2019 at 03:07:45PM -0500, Bjorn Helgaas wrote: > On Fri, Feb 08, 2019 at 10:24:12AM -0600, Alexandru Gagniuc wrote: > > We used to first parse all the _HPP and _HPX tables before using the > > information to program registers of PCIe devices. Up until HPX type 2, > > there was only

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 11:48 PM Christian Brauner wrote: > > On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione wrote: > > > > On Fri, Apr 19, 2019 at 1:57 PM Christian Brauner > > wrote: > > > > > > On Fri, Apr 19, 2019 at 10:34 PM Daniel Colascione > > > wrote: > > > > > > > > On Fri, Apr

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 2:45 PM Joel Fernandes wrote: > > On Fri, Apr 19, 2019 at 02:24:09PM -0700, Daniel Colascione wrote: > > On Fri, Apr 19, 2019 at 2:20 PM Joel Fernandes > > wrote: > > > > > > On Fri, Apr 19, 2019 at 10:57:11PM +0200, Christian Brauner wrote: > > > > On Fri, Apr 19, 2019

Re: [PATCH v4 2/9] clkdev: Move clk creation outside of 'clocks_mutex'

Quoting Stephen Boyd (2019-04-12 11:31:43) > We don't need to hold the 'clocks_mutex' here when we're creating a clk > pointer from a clk_lookup structure. Instead, we just need to make sure > that the lookup doesn't go away while we dereference the lookup pointer > to extract the clk_hw pointer

Re: [PATCH v4 3/9] clk: Prepare for clk registration API that uses DT nodes

Quoting Stephen Boyd (2019-04-12 11:31:44) > Split out the body of the clk_register() function so it can be shared > between the different types of registration APIs (DT, device). > > Cc: Miquel Raynal > Cc: Jerome Brunet > Cc: Russell King > Cc: Michael Turquette > Cc: Jeffrey Hugo > Cc:

Re: [PATCH v4 6/9] clk: Allow parents to be specified without string names

Quoting Stephen Boyd (2019-04-12 11:31:47) > The common clk framework is lacking in ability to describe the clk > topology without specifying strings for every possible parent-child > link. There are a few drawbacks to the current approach: > > 1) String comparisons are used for everything,

Re: [PATCH v4 5/9] clk: Add of_clk_hw_register() API for early clk drivers

Quoting Stephen Boyd (2019-04-12 11:31:46) > In some circumstances drivers register clks early and don't have access > to a struct device because the device model isn't initialized yet. Add > an API to let drivers register clks associated with a struct device_node > so that these drivers can

Re: [PATCH v4 9/9] clk: fixed-factor: Let clk framework find parent

Quoting Stephen Boyd (2019-04-12 11:31:50) > Convert this driver to a more modern way of specifying parents now that > we have a way to specify clk parents by DT index. This lets us nicely > avoid a problem where a parent clk name isn't know because the parent > clk hasn't been registered yet. >

Re: [PATCH v4 4/9] driver core: Let dev_of_node() accept a NULL dev

Quoting Stephen Boyd (2019-04-12 11:31:45) > We'd like to chain this in places where the 'dev' argument might be > NULL. Let this function take a NULL 'dev' so this can work. > > Cc: Miquel Raynal > Cc: Jerome Brunet > Cc: Russell King > Cc: Michael Turquette > Cc: Jeffrey Hugo > Cc: Chen-Yu

Re: [PATCH v4 7/9] clk: Look for parents with clkdev based clk_lookups

Quoting Stephen Boyd (2019-04-12 11:31:48) > In addition to looking for DT based parents, support clkdev based > clk_lookups. This should allow non-DT based clk drivers to participate > in the parent lookup process. > > Cc: Miquel Raynal > Cc: Jerome Brunet > Cc: Russell King > Cc: Michael

Re: [PATCH v4 8/9] clk: Allow parents to be specified via clkspec index

Quoting Stephen Boyd (2019-04-12 11:31:49) > Some clk providers are simple DT nodes that only have a 'clocks' > property without having an associated 'clock-names' property. In these > cases, we want to let these clk providers point to their parent clks > without having to dereference the 'clocks'

[PATCH 1/2] ARM: errata: Workaround errata A12 857271 / A17 857272

From: Sonny Rao This adds support for working around errata A12 857271 / A17 857272. These errata were causing hangs on rk3288-based Chromebooks and it was confirmed that this workaround fixed the problems. In the Chrome OS 3.14 kernel [1] this erratum was known as ERRATA_FOOBAR due to lack of

[PATCH 2/2] ARM: errata: add support for A12/A17 errata CR711784

This adds a code for turning on chicken bit 11, which appears to avoid a potential CPU deadlock that could occur. The exact set of instruction needed to trigger this errata is not totaly known but we have a high level of confidence that the problem is fixed by setting chicken bit 11. All details

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Sat, Apr 20, 2019 at 12:08 AM Daniel Colascione wrote: > > On Fri, Apr 19, 2019 at 2:45 PM Joel Fernandes wrote: > > > > On Fri, Apr 19, 2019 at 02:24:09PM -0700, Daniel Colascione wrote: > > > On Fri, Apr 19, 2019 at 2:20 PM Joel Fernandes > > > wrote: > > > > > > > > On Fri, Apr 19, 2019

Re: [PATCH RESEND] clk: tegra: Don't enable already enabled PLLs

Quoting Dmitry Osipenko (2019-04-19 04:42:26) > Initially Common Clock Framework isn't aware of the clock-enable status, > this results in enabling of clocks that were enabled by bootloader. This > is not a big deal for a regular clock-gates, but for PLL's it may have > some unpleasant

Re: [PATCH v2] clk: hi3660: Mark clk_gate_ufs_subsys as critical

Quoting Leo Yan (2019-03-20 03:05:08) > clk_gate_ufs_subsys is a system bus clock, turning off it will > introduce lockup issue during system suspend flow. Let's mark > clk_gate_ufs_subsys as critical clock, thus keeps it on during > system suspend and resume. > > Fixes: d374e6fd5088 ("clk:

Re: [PATCH] KVM: nVMX: allow tests to use bad virtual-APIC page address

On 04/15/2019 06:35 AM, Paolo Bonzini wrote: As mentioned in the comment, there are some special cases where we can simply clear the TPR shadow bit from the CPU-based execution controls in the vmcs02. Handle them so that we can remove some XFAILs from vmx.flat. Signed-off-by: Paolo Bonzini

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 2:48 PM Christian Brauner wrote: > > On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione wrote: > > > > On Fri, Apr 19, 2019 at 1:57 PM Christian Brauner > > wrote: > > > > > > On Fri, Apr 19, 2019 at 10:34 PM Daniel Colascione > > > wrote: > > > > > > > > On Fri, Apr

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 3:18 PM Christian Brauner wrote: > > On Sat, Apr 20, 2019 at 12:08 AM Daniel Colascione wrote: > > > > On Fri, Apr 19, 2019 at 2:45 PM Joel Fernandes > > wrote: > > > > > > On Fri, Apr 19, 2019 at 02:24:09PM -0700, Daniel Colascione wrote: > > > > On Fri, Apr 19, 2019

[PATCH] mm/hmm: Fix initial PFN for hugetlbfs pages

From: Ralph Campbell The mmotm patch [1] adds hugetlbfs support for HMM but the initial PFN used to fill the HMM range->pfns[] array doesn't properly compute the starting PFN offset. This can be tested by running test-hugetlbfs-read from [2]. Fix the PFN offset by adjusting the page offset by

Re: [PATCH] ACPI / LPSS: Don't skip late system PM ops for hibernate on BYT/CHT

On 4/18/19 5:42 AM, Hans de Goede wrote: >> On 4/8/19 2:16 AM, Hans de Goede wrote:> >>> >>> Hmm, interesting so you have hibernation working on a T100TA >>> (with 5.0 + 02e45646d53b reverted), right ? >>> > Still since my patch is regressing things for you I will try to > take a look at this

[PATCHv3] selftests/efivarfs: clean up test files from test_create*()

Test files created by test_create() and test_create_empty() tests will stay in the $efivarfs_mount directory until the system was rebooted. When the tester tries to run this efivarfs test again on the same system, the immutable characteristics in that directory will cause some "Operation not

Re: [PATCHv2] selftests/efivarfs: clean up test files from test_create*()

Hello, Commit f8a0590f fix some part of this issue. I will send out V3 base on this commit in linux-kselftest next branch. Thank you. On Fri, Apr 19, 2019 at 9:20 PM shuah wrote: > > On 4/19/19 7:12 AM, Po-Hsu Lin wrote: > > Test files created by test_create*() tests will stay in the > >

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 3:02 PM Christian Brauner wrote: > > On Fri, Apr 19, 2019 at 11:48 PM Christian Brauner > wrote: > > > > On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione > > wrote: > > > > > > On Fri, Apr 19, 2019 at 1:57 PM Christian Brauner > > > wrote: > > > > > > > > On Fri,

[PATCHv2] selftests/efivarfs: clean up test files from test_create*()

Test files created by test_create*() tests will stay in the $efivarfs_mount directory unless the system was rebooted. When the tester tries to run this efivarfs test again on the same system, the immutable characteristics in that directory will cause some "Operation not permitted" noises and a

DISCONTIGMEM is deprecated

On Fri, Apr 19, 2019 at 10:43:35AM +0100, Mel Gorman wrote: > DISCONTIG is essentially deprecated and even parisc plans to move to > SPARSEMEM so there is no need to be fancy, this patch simply disables > watermark boosting by default on DISCONTIGMEM. I don't think parisc is the only arch which

Re: [PATCH v4 14/16] locking/rwsem: Guard against making count negative

On Fri, Apr 19, 2019 at 02:02:07PM +0200, Peter Zijlstra wrote: > On Fri, Apr 19, 2019 at 12:26:47PM +0200, Peter Zijlstra wrote: > > I thought of a horrible horrible alternative: > > Hurm, that's broken as heck. Let me try again. So I can't make that scheme work, it all ends up wanting to have

[PATCH 2/2] docs: hwmon: remove the extension from .rst files

On almost all places, we're including ReST files without the extension. Let's remove the extension here as well, in order to use just one standard. Suggested-by: Jani Nikula --- Documentation/hwmon/index.rst | 316 +- 1 file changed, 158 insertions(+), 158

Re: [patch V2 28/29] stacktrace: Provide common infrastructure

On Thu, Apr 18, 2019 at 05:42:55PM +0200, Thomas Gleixner wrote: > On Thu, 18 Apr 2019, Josh Poimboeuf wrote: > > Another idea I had (but never got a chance to work on) was to extend the > > x86 unwind interface to all arches. So instead of the callbacks, each > > arch would implement something

Re: [PATCH v4 14/16] locking/rwsem: Guard against making count negative

On Fri, Apr 19, 2019 at 12:26:47PM +0200, Peter Zijlstra wrote: > I thought of a horrible horrible alternative: Hurm, that's broken as heck. Let me try again.

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Sat, Apr 20, 2019 at 12:35 AM Daniel Colascione wrote: > > On Fri, Apr 19, 2019 at 2:48 PM Christian Brauner > wrote: > > > > On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione > > wrote: > > > > > > On Fri, Apr 19, 2019 at 1:57 PM Christian Brauner > > > wrote: > > > > > > > > On Fri,

Re: [PATCH v4 2/2] power_supply: platform/chrome: wilco_ec: Add charging config driver

Hi Nick, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v5.1-rc5 next-20190418] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: Detecting x86 LAPIC timer frequency from CPUID data

On Fri, 19 Apr 2019 22:52:01 +0200 (CEST) Thomas Gleixner wrote: > On Fri, 19 Apr 2019, Jacob Pan wrote: > > On Fri, 19 Apr 2019 10:57:10 +0200 (CEST) > > Thomas Gleixner wrote: > > > On Fri, 19 Apr 2019, Daniel Drake wrote: > > > > 0x7F vs 0x7FFF, is that intentional? > > > >

Re: [PATCH 2/3] ARM: at91: move platform-specific asm-offset.h to arch/arm/mach-at91

On Sat, Apr 20, 2019 at 4:03 AM Ludovic Desroches wrote: > > On Mon, Apr 15, 2019 at 05:14:50PM +0200, Alexandre Belloni wrote: > > External E-Mail > > > > > > On 08/04/2019 16:54:26+0900, Masahiro Yamada wrote: > > > is only generated and included > > > by arch/arm/mach-at91/, so it does not

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 2:20 PM Joel Fernandes wrote: > > According to Linus, POLLHUP usually indicates that something is readable: Note that if you use the legacy interfaces (ie "select()"), then even just a plain POLLHUP will always just show as "readable". So for a lot of applications, it

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Sat, Apr 20, 2019 at 12:46 AM Daniel Colascione wrote: > > On Fri, Apr 19, 2019 at 3:02 PM Christian Brauner > wrote: > > > > On Fri, Apr 19, 2019 at 11:48 PM Christian Brauner > > wrote: > > > > > > On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione > > > wrote: > > > > > > > > On Fri,

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Sat, Apr 20, 2019 at 1:11 AM Linus Torvalds wrote: > > On Fri, Apr 19, 2019 at 2:20 PM Joel Fernandes wrote: > > > > According to Linus, POLLHUP usually indicates that something is readable: > > Note that if you use the legacy interfaces (ie "select()"), then even > just a plain POLLHUP will

Re: [RFC][PATCH 13/16] sched: Add core wide task selection and scheduling.

On 4/19/19 1:40 AM, Ingo Molnar wrote: * Subhra Mazumdar wrote: I see similar improvement with this patch as removing the condition I earlier mentioned. So that's not needed. I also included the patch for the priority fix. For 2 DB instances, HT disabling stands at -22% for 32 users (from

[PATCH] selftests: build and run gpio when output directory is the src dir

Build and run gpio when output directory is the src dir. gpio has dependency on tools/gpio and builds tools/gpio objects in the src directory in all cases making the src repo dirty even when object relocation is specified. This fixes the following commands from generating gpio objects in the

[PATCH] Makefile: add kselftest-build target

One of the use-cases is building kselftest and then installing. Adding a target to just build the tests from the main Makefile will help users and makes it easier. Signed-off-by: Shuah Khan --- Makefile | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Makefile b/Makefile index

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 4:02 PM Christian Brauner wrote: > > On Sat, Apr 20, 2019 at 12:35 AM Daniel Colascione wrote: > > > > On Fri, Apr 19, 2019 at 2:48 PM Christian Brauner > > wrote: > > > > > > On Fri, Apr 19, 2019 at 11:21 PM Daniel Colascione > > > wrote: > > > > > > > > On Fri, Apr

[RESEND PATCH] mm/hmm: Fix initial PFN for hugetlbfs pages

From: Ralph Campbell The mmotm patch [1] adds hugetlbfs support for HMM but the initial PFN used to fill the HMM range->pfns[] array doesn't properly compute the starting PFN offset. This can be tested by running test-hugetlbfs-read from [2]. Fix the PFN offset by adjusting the page offset by

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 4:33 PM Linus Torvalds wrote: > > On Fri, Apr 19, 2019 at 4:20 PM Christian Brauner > wrote: > > > > On Sat, Apr 20, 2019 at 1:11 AM Linus Torvalds > > wrote: > > > > > > It's also worth noting that POLLERR/POLLHUP/POLLNVAL cannot be masked > > > for "poll()". Even if

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 4:20 PM Christian Brauner wrote: > > On Sat, Apr 20, 2019 at 1:11 AM Linus Torvalds > wrote: > > > > It's also worth noting that POLLERR/POLLHUP/POLLNVAL cannot be masked > > for "poll()". Even if you only ask for POLLIN/POLLOUT, you will always > > get POLLERR/POLLHUP

Re: [GIT PULL] percpu changes for v5.1-rc6

The pull request you sent on Fri, 19 Apr 2019 17:29:18 -0400: > git://git.kernel.org/pub/scm/linux/kernel/git/dennis/percpu.git for-5.1-fixes has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/4c3f49ae1306c05e91211c06feddfd0a4a57fabd Thank you! -- Deet-doot-dot, I am a

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 4:12 PM Christian Brauner wrote: > > On Sat, Apr 20, 2019 at 12:46 AM Daniel Colascione wrote: > > > > On Fri, Apr 19, 2019 at 3:02 PM Christian Brauner > > wrote: > > > > > > On Fri, Apr 19, 2019 at 11:48 PM Christian Brauner > > > wrote: > > > > > > > > On Fri, Apr

[PATCHv2] since cmdline args can be same for multiple kexec, log entry hash will collide. Prepend the kernel file name to the cmdline args to distinguish between cmdline args passed to subsequent kexe

From: Prakhar Srivastava Signed-off-by: Prakhar Srivastava --- since cmdline args can be same for multiple kexec, log entry hash will collide. Prepend the kernel file name to the cmdline args to distinguish between cmdline args passed to subsequent kexec calls kernel/kexec_core.c | 57

[PATCHv2] use event name instead of enum to make the call generic

From: Prakhar Srivastava Signed-off-by: Prakhar Srivastava --- remove enaums to control type of buffers entries, instead pass the event name to be used. include/linux/ima.h | 10 ++ kernel/kexec_file.c | 3 +++ security/integrity/ima/ima.h | 2 +-

[PATCHv2] added ima hook for buffer, being enabled as a policy

From: Prakhar Srivastava Signed-off-by: Prakhar Srivastava --- This adds a new ima hook ima_buffer_check and a policy entry BUFFER_CHECK. This enables buffer has measurements into ima log Documentation/ABI/testing/ima_policy | 1 + include/linux/ima.h | 13 +++-

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Sat, Apr 20, 2019 at 1:30 AM Daniel Colascione wrote: > > On Fri, Apr 19, 2019 at 4:02 PM Christian Brauner > wrote: > > > > On Sat, Apr 20, 2019 at 12:35 AM Daniel Colascione > > wrote: > > > > > > On Fri, Apr 19, 2019 at 2:48 PM Christian Brauner > > > wrote: > > > > > > > > On Fri,

[PATCH v2 1/3 RFC] added ima hook for buffer, being enabled as a policy

From: Prakhar Srivastava Signed-off-by: Prakhar Srivastava --- Currently for soft reboot(kexec_file_load) the kernel file and signature is measured by IMA. The cmdline args used to load the kernel is not measured. The boot aggregate that gets calculated will have no change since the EFI loader

[PATCH v2 2/3 RFC] use event name instead of enum to make the call generic

From: Prakhar Srivastava Signed-off-by: Prakhar Srivastava --- Currently for soft reboot(kexec_file_load) the kernel file and signature is measured by IMA. The cmdline args used to load the kernel is not measured. The boot aggregate that gets calculated will have no change since the EFI loader

[PATCH v2 3/3 RFC] since cmdline args can be same for multiple kexec, log entry hash will collide. Prepend the kernel file name to the cmdline args to distinguish between cmdline args passed to subseq

From: Prakhar Srivastava Signed-off-by: Prakhar Srivastava --- Currently for soft reboot(kexec_file_load) the kernel file and signature is measured by IMA. The cmdline args used to load the kernel is not measured. The boot aggregate that gets calculated will have no change since the EFI loader

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Sat, Apr 20, 2019 at 1:47 AM Daniel Colascione wrote: > > On Fri, Apr 19, 2019 at 4:12 PM Christian Brauner > wrote: > > > > On Sat, Apr 20, 2019 at 12:46 AM Daniel Colascione > > wrote: > > > > > > On Fri, Apr 19, 2019 at 3:02 PM Christian Brauner > > > wrote: > > > > > > > > On Fri,

Re: [PATCH] Documentation: atomic_t.txt: Explain ordering provided by smp_mb__{before,after}_atomic()

Paul E. McKenney's on April 20, 2019 4:26 am: > On Fri, Apr 19, 2019 at 08:00:17PM +0200, Peter Zijlstra wrote: >> On Fri, Apr 19, 2019 at 01:21:45PM -0400, Alan Stern wrote: >> > Index: usb-devel/Documentation/atomic_t.txt >> > ===

[tip:WIP.x86/alternatives 2/9] kernel/jump_label.c:387:10-11: WARNING: return of 0/1 in function 'jump_label_can_update_check' with return type bool

tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/alternatives head: 1f30946b1a01baf22df6faf74c0a1e602bb6cac7 commit: 41bef31d0abe29b5888b33b526cacc8a30795318 [2/9] jump_label: Add the jump_label_can_update_check() helper If you fix the issue, kindly add following

[GIT PULL] cgroup fix for v5.1-rc5

Hello, Linus. A patch to fix a RCU imbalance error in the devices cgroup configuration error path. Thanks. The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b: Linux 5.1-rc1 (2019-03-17 14:22:26 -0700) are available in the Git repository at:

Re: Urgent Reply

Dear friend, I am the Head of file Department in Africa Develop bank Burkina Faso. I need your sincere cooperation to transfer the sum of $15 million U.S.A dollars to your bank account. I want you stand as next of kin to the deceased. I agree 40% for you and 60% for me. Upon receipt of your

[PATCH] dcache: ensure d_flags & d_inode are consistent in lookup_fast()

After extending the size of dentry from 192-bytes to 208-bytes under aarch64, we got oops during the running of xfstests generic/429: Unable to handle kernel NULL pointer dereference at virtual address 0002 CPU: 3 PID: 2725 Comm: t_encrypted_d_r Tainted: G D

Re: [PATCH] kexec_buffer measure

Currently for soft reboot(kexec_file_load) the kernel file and signature is measured by IMA. The cmdline args used to load the kernel is not measured. The boot aggregate that gets calculated will have no change since the EFI loader has not been triggered. Adding the kexec cmdline args measure and

Re: [PATCH 3/6] y2038: linux: Provide __clock_settime64 implementation

15.04.2019 в 00:08:38 +0200 Lukasz Majewski написал: > +# if defined __NR_clock_settime64 > + /* Make sure that passed __timespec64 struct pad is 0. */ > + struct __timespec64 ts = *tp; > + ts.tv_pad = 0; > + return INLINE_SYSCALL_CALL (clock_settime64, clock_id, ); Isn't kernel supposed to

Re: [PATCH RFC 1/2] Add polling support to pidfd

On Fri, Apr 19, 2019 at 04:11:37PM -0700, Linus Torvalds wrote: > On Fri, Apr 19, 2019 at 2:20 PM Joel Fernandes wrote: > > > > According to Linus, POLLHUP usually indicates that something is readable: > > Note that if you use the legacy interfaces (ie "select()"), then even > just a plain

Re: [GIT PULL] cgroup fix for v5.1-rc5

The pull request you sent on Fri, 19 Apr 2019 17:28:34 -0700: > git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-5.1-fixes has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/371dd432ab39f7bc55d6ec77d63b430285627e04 Thank you! -- Deet-doot-dot, I am a

Re: [PATCH 4.9 00/50] 4.9.170-stable review

On Fri, Apr 19, 2019 at 01:16:37PM -0700, Guenter Roeck wrote: On Fri, Apr 19, 2019 at 12:39:26PM -0700, Guenter Roeck wrote: On Thu, Apr 18, 2019 at 07:57:11PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.170 release. > There are 50 patches in

Re: [PATCH v2] clk: hi3660: Mark clk_gate_ufs_subsys as critical

On Fri, Apr 19, 2019 at 03:20:42PM -0700, Stephen Boyd wrote: > Quoting Leo Yan (2019-03-20 03:05:08) > > clk_gate_ufs_subsys is a system bus clock, turning off it will > > introduce lockup issue during system suspend flow. Let's mark > > clk_gate_ufs_subsys as critical clock, thus keeps it on

[PATCH] HID: intel-ish-hid: Add Comet Lake PCI device ID

Added Comet Lake PCI device ID to the supported device list. Signed-off-by: Srinivas Pandruvada --- drivers/hid/intel-ish-hid/ipc/hw-ish.h | 1 + drivers/hid/intel-ish-hid/ipc/pci-ish.c | 1 + 2 files changed, 2 insertions(+) diff --git a/drivers/hid/intel-ish-hid/ipc/hw-ish.h

Re: [PATCH 5/6] ARM: ks8695, serial: skip manual tx IRQ ack

Hi Arnd, On 16/4/19 6:24 am, Arnd Bergmann wrote: The TX interrupt is marked as edge triggered, so it will already be acked by the top-level irq code, and does not need the ack in the driver. Removing this avoids a nasty dependency on the regs-irq.h file that is otherwise reserved for the

[PATCH] tracing: Fix a memory leak bug

In trace_pid_write(), the buffer for trace parser is allocated through kmalloc() in trace_parser_get_init(). Later on, after the buffer is used, it is then freed through kfree() in trace_parser_put(). However, it is possible that trace_pid_write() is terminated due to unexpected errors, e.g.,

Re: [tip:core/rseq] rseq/selftests/x86: Work around bogus gcc-8 optimisation

- On Apr 19, 2019, at 5:13 PM, Mathieu Desnoyers mathieu.desnoy...@efficios.com wrote: > - On Apr 19, 2019, at 2:53 PM, Linus Torvalds > torva...@linux-foundation.org > wrote: > >> On Fri, Apr 19, 2019 at 11:46 AM tip-bot for Mathieu Desnoyers >> wrote: >>> >>> rseq/selftests/x86:

<    1   2   3   4   5   6   >