tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 7142eaa58b49d9de492ccc16d48df7c488a5fbb6
commit: 62129a0849d27cc94ced832bcf9dcde283dcbe08 iio: chemical: sps30: allow
changing self cleaning period
date: 3 months ago
reproduce:
# apt-get install s
Remove flush_tlb_info variables from the stack. This allows to align
flush_tlb_info to cache-line and avoid potentially unnecessary cache
line movements. It also allows to have a fixed virtual-to-physical
translation of the variables, which reduces TLB misses.
Use per-CPU struct for flush_tlb_mm_r
On Tue 23-04-19 06:24:53, Yang Shi wrote:
> The commit 7635d9cbe832 ("mm, thp, proc: report THP eligibility for each
> vma") introduced THPeligible bit for processes' smaps. But, when checking
> the eligibility for shmem vma, __transparent_hugepage_enabled() is
> called to override the result from
On 2019-04-22, Hongzhi, Song wrote:
> Anyone notice this issue?
Yes, I am aware of the issue. It is actually a feature, not a bug. ;-)
Individual LOG_CONT messages, when classified as emergency messages, are
printed immediately to the console. This makes them appear
"disorderly". It is not yet c
On Mon, 2019-04-22 at 23:06 +0200, Greg KH wrote:
>
>
> On Mon, Apr 22, 2019 at 11:32:56AM +0300, Alexandru Ardelean wrote:
> > This helper is similar to __sysfs_match_string() with the exception
> > that it
> > ignores NULL elements within the array.
>
> sysfs is "one value per file", why are y
On 4/19/19 11:43 AM, Mel Gorman wrote:
> Mikulas Patocka reported that 1c30844d2dfe ("mm: reclaim small amounts
> of memory when an external fragmentation event occurs") "broke" memory
> management on parisc. The machine is not NUMA but the DISCONTIG model
> creates three pgdats even though it's a
On Tue, 16 Apr 2019 at 20:33, Raul E Rangel wrote:
>
> I am not able to make a single event class for all these registers. They
> all have different struct sizes and different printf formats.
>
> Thanks for the reviews!
>
> Changes in v2:
> - Made trace_sd_scr print out flags.
> - Add BUILD_BUG_ON
Petr, Steven,
RFC
Normally, we grab console_sem lock before we iterate consoles
list, which is necessary if we want to be race free. The only exception
to this rule is console_flush_on_panic(). However, it seems that we are
not fully race free - register_console() iterates console
The following pattern is not completely safe:
for_each_console(bcon)
if (bcon->flags & CON_BOOT)
unregister_console(bcon);
Because, in theory, console drivers list and console drivers
can be modified concurrently from another CPU. Take console_sem
lock, which protects c
We need to take console_sem lock when we iterate console
drivers list. Otherwise, another CPU can concurrently
modify console drivers list or console drivers.
Signed-off-by: Sergey Senozhatsky
---
kernel/printk/printk.c | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
Hi Marco,
On Tue, Apr 23, 2019 at 8:19 AM Marco Felsch wrote:
>
> Hi Daniel,
>
> On 19-04-22 19:36, Daniel Baluta wrote:
> > i.MX8MM has one wm8524 audio codec connected with
> > SAI3 digital audio interface.
> >
> > This patch uses simple-card machine driver in order
> > to enable wm8524 codec.
Good afternoon from Singapore,
May I know where is the PGP verification signature for Linux kernel 5.1-rc6? I
can't find it at https://www.kernel.org/
Please advise.
Thank you very much.
-BEGIN EMAIL SIGNATURE-
The Gospel for all Targeted Individuals (TIs):
[The New York Ti
On Tue, Apr 23, 2019 at 8:21 AM Marco Felsch wrote:
>
> Hi Daniel,
>
> On 19-04-22 19:35, Daniel Baluta wrote:
> > i.MX8MM has 5 SAI instances with the following base
> > addresses according to RM.
> >
> > SAI1 base address: 3001_h
> > SAI2 base address: 3002_h
> > SAI3 base address: 3003_
On 一, 2019-04-22 at 09:44 -0700, Wei Wang wrote:
> On Mon, Apr 22, 2019 at 2:03 AM Zhang Rui
> wrote:
> >
> >
> > On 二, 2019-04-16 at 10:07 -0700, Wei Wang wrote:
> > >
> > > It is unnecessary to update disabled thermal zones post suspend
> > > and
> > > sometimes leads error/warning in bad beh
On Tue, Apr 23, 2019 at 09:58:19AM +0800, Lu Baolu wrote:
> 554 for (i = 0; i < nslots; i++)
> 555 io_tlb_orig_addr[index+i] = orig_addr + (i <<
> IO_TLB_SHIFT);
>
> Could the tlb orig address set to PAGE_ALIGN_DOWN(orig_addr)? We
> couldn't assume the bounce buffer just st
There are issues with interrupt handling in rcar_gen3_thermal driver.
Currently IRQ is remain enabled after .remove, later if device is probed,
IRQ is requested before .thermal_init, this may cause IRQ function be
triggered but not able to clear IRQ status, thus cause system to hang.
Since the ir
Currently IRQ is remain enabled after .remove, later if device is probed,
IRQ is requested before .thermal_init, this may cause IRQ function be
called before device is initialized.
this patch by disable interrupt in .remove, to ensure irq function
only be called after device is fully initialized.
On 23/04/19 11:36 AM, Vignesh Raghavendra wrote:
>
>
> Vignesh Raghavendra (5):
> mtd: cfi_cmdset_0002: Add support for polling status register
> dt-bindings: mtd: Add binding documentation for HyperFlash
> mtd: Add support for HyperBus memory devices
> dt-bindings: mtd: Add bindings f
Currently IRQF_SHARED type interrupt line is allocated, but it
is not appropriate, as the interrupt line isn't shared between
different devices, instead IRQF_ONESHOT is the proper type.
By changing interrupt type to IRQF_ONESHOT, now irq handler is
no longer needed, as clear of interrupt status ca
On 4/22/2019 1:24 PM, Jisheng Zhang wrote:
On Wed, 17 Apr 2019 09:56:33 + Gustavo Pimentel wrote:
On Tue, Apr 16, 2019 at 20:27:18, Vidya Sagar wrote:
Remove multiple write enable and disable sequences of dbi registers as
Tegra194 implements writes to BAR-0 register (offset: 0x10) contr
Cypress' HyperBus is Low Signal Count, High Performance Double Data Rate
Bus interface between a host system master and one or more slave
interfaces. HyperBus is used to connect microprocessor, microcontroller,
or ASIC devices with random access NOR flash memory (called HyperFlash)
or self refresh
Add DT binding documentation for HyperFlash devices.
Signed-off-by: Vignesh Raghavendra
---
.../devicetree/bindings/mtd/cypress,hyperflash.txt | 6 ++
1 file changed, 6 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mtd/cypress,hyperflash.txt
diff --git a/Docum
HyperFlash devices are compliant with CFI AMD/Fujitsu Extended Command
Set(0x0002) for flash operations, therefore drivers/mtd/chips/cfi_cmdset_0002.c
can be used as is. But these devices do not support DQ polling method of
determining chip ready/good status. These flashes provide Status
Register w
Add binding documentation for TI's HyperBus memory controller present on
AM654 SoC.
Signed-off-by: Vignesh Raghavendra
---
.../devicetree/bindings/mtd/ti,am654-hbmc.txt | 31 +++
MAINTAINERS | 1 +
2 files changed, 32 insertions(+)
create mode
Add driver for HyperBus memory controller on TI's AM654 SoC. Programming
IP is pretty simple and provides direct memory mapped access to
connected Flash devices.
Add basic support for the IP without DMA. Second chipSelect is not
supported for now.
Signed-off-by: Vignesh Raghavendra
---
drivers/
Cypress HyperBus is Low Signal Count, High Performance Double Data Rate Bus
interface between a host system master and one or more slave interfaces.
HyperBus is used to connect microprocessor, microcontroller, or ASIC
devices with random access NOR flash memory(called HyperFlash) or
self refresh DR
Hi, Daniel,
thanks for clarifying.
It is true that we need to make thermal framework ready as early as
possible. And a static table works for me as long as vmlinux.lds.h is
the proper place.
Arnd,
are you okay with this patch? if yes, I suppose I can take it through
my tree, right?
thanks,
rui
Dear Greg,
This is extcon-next pull request for v5.2. I add detailed description of
this pull request on below. Please pull extcon with following updates.
[Detailed description for this pull request]
1. Add new extcon-intel-mrfld.c extcon provider driver
- On Intel Merrifield the Basin Cove PMIC
On Tue, Apr 23, 2019 at 08:13:48AM +0800, Guo Ren wrote:
> > We should probably start a working group for this ASAP unless we can
> > get another working group to help taking care of it.
> Good news, I prefer to use instructions directly instead of SBI_CALL.
>
> Our instruction is "dcache.c/iva %0
Hi Sasha,
On Mon, Apr 22, 2019 at 03:47:19PM -0400, Sasha Levin wrote:
> From: Fabien Dessenne
>
> [ Upstream commit f4e68d58cf2b20a581759bbc7228052534652673 ]
>
> Unlike 'client_ops' which is initialized to 'default_client_ops', the
> port operations 'ops' may be left to NULL.
> Check the 'ops
Hi Angus,
looks good to me just a few last nitpicks. Feel free to add or drop it.
Regards,
Marco
On 19-04-22 08:30, Angus Ainslie (Purism) wrote:
> This is the development kit board for the Librem 5. The current level of
> support yields a working console and is able to boot userspace from the
Hi Daniel,
On 19-04-22 19:35, Daniel Baluta wrote:
> i.MX8MM has 5 SAI instances with the following base
> addresses according to RM.
>
> SAI1 base address: 3001_h
> SAI2 base address: 3002_h
> SAI3 base address: 3003_h
> SAI5 base address: 3005_h
> SAI6 base address: 3006_h
>
Hi Daniel,
On 19-04-22 19:36, Daniel Baluta wrote:
> i.MX8MM has one wm8524 audio codec connected with
> SAI3 digital audio interface.
>
> This patch uses simple-card machine driver in order
> to enable wm8524 codec.
>
> We need to set:
> * SAI3 pinctrl configuration
> * clock hierar
Hi Greg,
After merging the staging tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/staging/kpc2000/kpc_spi/spi_driver.c:97:5: note: offset of packed
bit-field 'wl' has changed in GCC 4.4
} bitfield;
^
drivers/staging/kpc2000/kpc_spi/spi_driver.c:97:5
On 03-04-19, 12:23, Nicolas Ferre wrote:
> Even if this case shouldn't happen when controller is properly programmed,
> it's still better to avoid dumping a kernel Oops for this.
> As the sequence may happen only for debugging purposes, log the error and
> just finish the tasklet call.
Applied all
Modern Intel SoCs now include a special ITSSPRC register that can be
used to "gate" the PIT such that IRQ0 interrupts do not fire.
With Intel Apollo Lake we are starting to see consumer products that
have a BIOS option to apply this (defaulting to gated). Some such
products also lack the HPET ACPI
New products based on Intel Apollo Lake are appearing where the HPET is
not present in ACPI, and the legacy 8254 PIT is "gated" by default in
the BIOS setup menu.
This leads an early boot "IO-APIC + timer doesn't work!" kernel panic
on a black screen (before the framebuffer is initialized).
Avoid
Hi,
at 02:22, wrote:
Hi.
I've just applied this patch, and touchpad woorks smoothly, but suspend
issue is still present.
After suspend, i2c_hid module bursts i2c_hid i2c-ELAN1200:00:
i2c_hid_get_input: incomplete report (16/65535) messages (more than 50
reports/sec).
In dmesg I can see
Export all configuration space access APIs and also other APIs to
support host controller drivers of DesignWare core based implementations
while adding support for .remove() hook to build their respective drivers
as modules
Signed-off-by: Vidya Sagar
Acked-by: Gustavo Pimentel
---
v3:
* Rebased
Add an API to group all the tasks to be done to de-initialize host which
can then be called by any DesignWare core based driver implementations
while adding .remove() support in their respective drivers.
Signed-off-by: Vidya Sagar
Acked-by: Gustavo Pimentel
---
v3:
* Rebased on top of linux-next
On Tue, Apr 9, 2019 at 11:20 PM Tony Lindgren wrote:
>
> * Masahiro Yamada [190409 07:06]:
> > On Tue, Apr 9, 2019 at 2:17 PM Keerthy wrote:
> > >
> > >
> > >
> > > On 09/04/19 10:37 AM, Masahiro Yamada wrote:
> > > > On Tue, Apr 9, 2019 at 2:00 PM Keerthy wrote:
> > > >>
> > > >>
> > > >>
> >
On Sat, Apr 20, 2019 at 8:10 AM Masahiro Yamada
wrote:
>
> 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
On Tue, Apr 23, 2019 at 10:33 AM Stephen Rothwell wrote:
>
> Hi all,
>
> After merging the at91 tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> arch/arm/mach-at91/pm_suspend.S:17:10: fatal error: pm_data-offsets.h: No
> such file or directory
> #include "pm_data-o
On 2019/4/23 3:48, Paul Moore wrote:
On Sat, Apr 20, 2019 at 3:39 AM Yang Yingliang wrote:
I'm not sure you got my point.
I went back and looked at your previous emails again to try and
understand what you are talking about, and I'm a little confused by
some of the output ...
--- a/kernel
On Tue, Apr 23, 2019 at 07:30:36AM +1000, Stephen Rothwell wrote:
>
> In commit
>
> f5a2aeb8b254 ("crypto: ccp - Do not free psp_master when PLATFORM_INIT
> fails")
>
> Fixes tag
>
> Fixes: 200664d5237f ("crypto: ccp: Add SEV support")
>
> has these problem(s):
>
> - Subject does not m
I was looking into an issue on our distro kernel where allocation of huge
pages via "echo X > /proc/sys/vm/nr_hugepages" was taking a LONG time.
In this particular case, we were actually allocating huge pages VERY slowly
at the rate of about one every 30 seconds. I don't want to talk about the
cod
On Wed, Apr 17, 2019 at 03:42:41PM +0200, Paolo Bonzini wrote:
> If a memory slot's size is not a multiple of 64 pages (256K), then
> the KVM_CLEAR_DIRTY_LOG API is unusable: clearing the final 64 pages
> either requires the requested page range to go beyond memslot->npages,
> or requires log->num_
On Fri, Apr 19, 2019 at 02:13:48PM +0530, Mukesh Ojha wrote:
>
> On 4/19/2019 12:41 PM, dmitry.torok...@gmail.com wrote:
> > Hi Mukesh,
> >
> > On Fri, Apr 19, 2019 at 12:17:44PM +0530, Mukesh Ojha wrote:
> > > For some reason my last mail did not get delivered, sending it again.
> > >
> > >
>
On Mon, Apr 15, 2019 at 09:25:24PM +0200, Arnd Bergmann wrote:
> We can communicate the clock rate using platform data rather than setting
> a flag to use a particular value in the driver, which is cleaner and
> avoids the dependency.
>
> No platform in the kernel currently defines the ep93xx keyp
On April 19, 2019 10:07:14 AM GMT+09:00, Matthew Wilcox
wrote:
> On Fri, Apr 19, 2019 at 09:17:17AM +0900, Matteo Croce wrote:
> > > extern const int sysctl_zero;
> > > /* comment goes here */
> > > #define SYSCTL_ZERO ((void *)&sysctl_zero)
> > >
> > > and then use SYSCTL_ZERO everywhere. That
Thanks for the feedback. I'll probably update each patch subject with the
module names as well. I'll send a v2 for all three.
Thanks,
Joe
-Original Message-
From: Michael Kelley
Sent: Monday, April 22, 2019 11:16 PM
To: Joseph Salisbury ; KY Srinivasan
; Haiyang Zhang ; Stephen He
On 2019/4/23 2:35, Sean Christopherson wrote:
On Mon, Apr 22, 2019 at 02:40:34PM +0800, Like Xu wrote:
Expose Intel V2 Extended Topology Enumeration Leaf to guest only when
host system has multiple software-visible die within each package.
Signed-off-by: Like Xu
---
arch/x86/kvm/cpuid.c | 13
From: Joseph Salisbury Sent: Monday, April 22,
2019 2:31 PM
>
> Signed-off-by: Joseph Salisbury
> ---
> drivers/hid/hid-hyperv.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/hid/hid-hyperv.c b/drivers/hid/hid-hyperv.c
> index 704049e62d58..d3311d714d35 100644
> --- a/dri
On Mon, Apr 22, 2019 at 8:04 PM Ingo Molnar wrote:
> Minor style nit: the parentheses are unnecessary, integer expressions
> like this are evaluated left to right and multiplication and division has
> the same precedence.
Fair point, although the same could be said for cpu_khz_from_msr().
> But
On Mon, Apr 22, 2019 at 10:54:02AM -0400, Jerome Glisse wrote:
> On Mon, Apr 22, 2019 at 08:20:10PM +0800, Peter Xu wrote:
> > On Fri, Apr 19, 2019 at 11:02:53AM -0400, Jerome Glisse wrote:
> >
> > [...]
> >
> > > > > > + if (uffd_wp_resolve) {
> > > > > > +
Friendly ping...
On 2019/4/9 23:36, Yue Haibing wrote:
> From: YueHaibing
>
> Syzkaller report this:
>
> sysctl could not get directory: /net//bridge -12
> kasan: CONFIG_KASAN_INLINE enabled
> kasan: GPF could be caused by NULL-ptr deref or user memory access
> general protection fault: [#
Pointers should be printed with %p or %px rather than
cast to unsigned long type and printed with %lx.
Change %lx to %pK to print the pointers.
Signed-off-by: Fuqian Huang
---
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c | 8
1 file changed, 4 insertions(+), 4 deletions
Pointers should be printed with %p or %px rather than
cast to unsigned long type and printed with %lx.
Change %lx to %pK to print the pointers.
Signed-off-by: Fuqian Huang
---
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c | 8
1 file changed, 4 insertions(+), 4 deletions
Ls1088a has 2 thermal sensors, core cluster and SoC platform. Core cluster
sensor is used to monitor the temperature of core and SoC platform is for
platform. The current dts only support the first sensor.
This patch adds the second sensor node to dts to enable it.
Signed-off-by: Yuantian Tang
--
On Mon, Apr 22, 2019 at 09:59:47PM -0400, Paul Moore wrote:
> On Mon, Apr 22, 2019 at 5:00 PM Nathan Chancellor
> wrote:
> > Hi all,
> >
> > After a glibc update to 2.29, my 4.14 builds started failing like so:
>
> ...
>
> > HOSTCC scripts/selinux/genheaders/genheaders
> > In file included fr
On Spreadtrum platform, the audio subsystem will use the multi-channel
data transfer controller to transfer sound stream between audio subsystem
and other AP/CP subsystem.
It can support 10 DAC channel and 10 ADC channel, and each channel has
512 bytes depth data fifo. Moreover each channel can be
On Spreadtrum platform, the audio subsystem will use the multi-channel
data transfer controller to transfer sound stream between audio subsystem
and other AP/CP subsystem.
It can support 10 DAC channel and 10 ADC channel, and each channel has
512 bytes depth data fifo. Moreover each channel can be
There maybe cause potential string overflow issue due to use
strcpy without checking the length
Detected By CoversityScan CID# 1444760
Fixes: 131ac62253dba:(staging: most: core: use device description as name)
Signed-off-by: Bo YU
---
drivers/staging/most/core.c | 2 +-
1 file changed, 1 insert
On 2019/4/22 下午10:34, 禹舟键 wrote:
> Hi, Michael
> I really want to know how could you fix the conflict between numa balancer
> and load balancer. Maybe you gained numa bonus by migrating some tasks to the
> node with most of the cache there, but, cpu load balance was break, so how to
> do it ?
T
Hi Stephen,
On Tue, Apr 23, 2019 at 08:45:01AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> arch/arm/boot/dts/imx7d-zii-rpu2.dts:46.12-50.4: Warning
> (io_channels_property): /iio-hwmon: Mi
On Mon, Apr 22, 2019 at 5:00 PM Nathan Chancellor
wrote:
> Hi all,
>
> After a glibc update to 2.29, my 4.14 builds started failing like so:
...
> HOSTCC scripts/selinux/genheaders/genheaders
> In file included from scripts/selinux/genheaders/genheaders.c:19:
> ./security/selinux/include/clas
On Sun, Apr 14, 2019 at 11:34:00AM -0700, Andrey Smirnov wrote:
> Add #io-channel-cells to list of required properties. Needed to be
> able to reference that node by phandle.
>
> Signed-off-by: Andrey Smirnov
> Cc: Shawn Guo
> Cc: Chris Healy
> Cc: Andrew Lunn
> Cc: Fabio Estevam
> Cc: Rob He
On Sun, Apr 14, 2019 at 11:34:01AM -0700, Andrey Smirnov wrote:
> Specify #io-channel-cells in ADC nodes. Needed to be able to reference
> them by phandle.
>
> Signed-off-by: Andrey Smirnov
> Cc: Shawn Guo
> Cc: Chris Healy
> Cc: Andrew Lunn
> Cc: Fabio Estevam
> Cc: Rob Herring
> Cc: linux-
On Mon, Apr 22, 2019 at 06:29:06PM -0700, Andy Lutomirski wrote:
> On Mon, Apr 22, 2019 at 5:37 PM Cedric Xing wrote:
> >
> > Given the changes to __vdso_sgx_enter_enclave(), the selftest is augmented
> > to
> > test the newly added callback interface. This addtional test marks the whole
> > encl
__call_srcu() is only used in current file, just make it static.
Signed-off-by: Jiang Biao
---
kernel/rcu/srcutree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
index a60b8ba9e1ac..a2ade0c6cd87 100644
--- a/kernel/rcu/srcutree
On Mon, Apr 22, 2019 at 5:37 PM Cedric Xing wrote:
>
> Given the changes to __vdso_sgx_enter_enclave(), the selftest is augmented to
> test the newly added callback interface. This addtional test marks the whole
> enclave range as PROT_READ, and calls mprotect() upon #PFs to add necessary
> PTE
>
On Mon, Apr 22, 2019 at 5:37 PM Cedric Xing wrote:
>
> The previous __vdso_sgx_enter_enclave() requires enclaves to preserve %rsp,
> which prohibits enclaves from allocating and passing parameters for
> untrusted function calls (aka. o-calls).
>
> This patch addresses the problem above by introduc
On 4/22/19 3:57 PM, Kees Cook wrote:
Commit eab09532d400 ("binfmt_elf: use ELF_ET_DYN_BASE only for PIE"),
made changes in the rare case when the ELF loader was directly invoked
(e.g to set a non-inheritable LD_LIBRARY_PATH, testing new versions of
the loader), by moving into the mmap region to a
rdp is initialized but never used in synchronize_rcu_expedited(),
just remove it.
Signed-off-by: Jiang Biao
---
kernel/rcu/tree_exp.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/rcu/tree_exp.h b/kernel/rcu/tree_exp.h
index 4c2a0189e748..5772612379e4 100644
--- a/kernel/rcu/tree_e
hi,
在 2019/4/22 下午11:23, Doug Anderson 写道:
Elaine,
On Fri, Apr 12, 2019 at 9:18 AM Douglas Anderson wrote:
This is mostly a revert of commit 55bb6a633c33 ("clk: rockchip: mark
noc and some special clk as critical on rk3288") except that we're
keeping "pmu_hclk_otg0" as critical still.
NOTE:
Hi Zhenliang,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.1-rc6 next-20190418]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Quoting kernelci.org bot (2019-04-22 17:16:44)
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * This automated bisection report was sent to you on the basis *
> * that you may be involved with the breaking commit it has *
> * found. No manual investigation has been don
On Mon, Apr 22, 2019 at 3:09 PM Alexey Dobriyan wrote:
>
> On Mon, Apr 22, 2019 at 07:30:40AM -0700, Andy Lutomirski wrote:
> >
> >
> > > On Apr 22, 2019, at 3:34 AM, Ingo Molnar wrote:
> > >
> > >
> > > * Alexey Dobriyan wrote:
> > >
> > > +++ b/arch/x86/kernel/task_size_64.c
> > > @@ -
Quoting Jeffrey Hugo (2019-02-11 10:57:47)
> If a parent to a clock comes from outside that clock's provider, the parent
> may not be present at the time the clock is registered (ie the parent comes
> from another driver that has not yet probed). The clock can still be
> registered, and a referenc
Hi all,
Today's linux-next merge of the v4l-dvb-next tree got a conflict in:
drivers/media/platform/Kconfig
between commit:
63604a143fe1 ("media: seco-cec: fix building with RC_CORE=m")
from the v4l-dvb tree and commit:
81527254e151 ("media: seco: depend on CONFIG_RC_CORE=y when not a m
The original x86/sgx/Makefile doesn't work when 'x86/sgx' is specified as the
test target. This patch fixes that problem, along with minor changes to the
dependencies between 'x86' and 'x86/sgx' in selftests/x86/Makefile.
Signed-off-by: Cedric Xing
---
tools/testing/selftests/x86/Makefile |
The current proposed __vdso_sgx_enter_enclave() requires enclaves to preserve
%rsp, which prohibits enclaves from allocating space on the untrusted stack.
However, there are existing enclaves (e.g. those built with current Intel SGX
SDK libraries) relying on the untrusted stack for passing paramete
Given the changes to __vdso_sgx_enter_enclave(), the selftest is augmented to
test the newly added callback interface. This addtional test marks the whole
enclave range as PROT_READ, and calls mprotect() upon #PFs to add necessary PTE
permissions per PFEC (#PF Error Code) until the enclave finishes
The previous __vdso_sgx_enter_enclave() requires enclaves to preserve %rsp,
which prohibits enclaves from allocating and passing parameters for
untrusted function calls (aka. o-calls).
This patch addresses the problem above by introducing a new ABI that preserves
%rbp instead of %rsp. Then __vdso_
On Mon, 22 Apr 2019 19:05:57 -0500
Alex G wrote:
> On 4/22/19 5:43 PM, Alex Williamson wrote:
> > [ 329.725607] vfio-pci :07:00.0: 32.000 Gb/s available PCIe bandwidth,
> > limited by 2.5 GT/s x16 link at :00:02.0 (capable of 64.000 Gb/s with 5
> > GT/s x16 link)
> > [ 708.151488] vfio-
Hi,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.1-rc6 next-20190418]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/guoren-
[Cc'ing LSM mailing list]
On Fri, 2019-04-19 at 17:30 -0700, prakhar srivastava wrote:
> 2) Adding a LSM hook
> We are doing both the command line and kernel version measurement in IMA.
> Can you please elaborate on how this can be used outside of the scenario?
> That will help me come back with
I've heard from two separate people who have had trouble getting started
with BBL & open-source FSBL test flows with arbitrary DT files on the
Freedom Unleashed board. The following instructions should help get
people started.
The core issue, aside from general unfamiliarity, is that multipl
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis *
* that you may be involved with the breaking commit it has *
* found. No manual investigation has been done to verify it, *
* and the root cause of the problem
Platform core is using pdev->name as the platform device name to do
the binding of the devices with the drivers. But, when the platform
driver overrides the platform device name with dev_set_name(),
the pdev->name is pointing to a location which is freed and becomes
an invalid parameter to do the b
Thx Christoph,
On Mon, Apr 22, 2019 at 06:18:14PM +0200, Christoph Hellwig wrote:
> On Mon, Apr 22, 2019 at 11:44:30PM +0800, guo...@kernel.org wrote:
> > - Add _PAGE_COHERENCY bit in current page table entry attributes. The bit
> >designates a coherence for this page mapping. Software set th
On 4/22/19 5:43 PM, Alex Williamson wrote:
[ 329.725607] vfio-pci :07:00.0: 32.000 Gb/s available PCIe bandwidth,
limited by 2.5 GT/s x16 link at :00:02.0 (capable of 64.000 Gb/s with 5
GT/s x16 link)
[ 708.151488] vfio-pci :07:00.0: 32.000 Gb/s available PCIe bandwidth,
limited by
In some situations (described below), hierarchies of 32-bit resources can
fail to be assigned when the kernel has to attempt to assign a large
64-bit resource. When this happens, lspci will report
some PCI BAR resources as 'ignored' and some PCI Bridge windows
being left unset. Sample lspci lines m
Hey,
This is largely a resend to get some more attention. I've attempted to clean
up and expand on the commit message of the first commit because the
bug is a bit of a nightmare to explain and follow. There's a lot more
information on the first commit in the original thread here[1] including
instr
One odd quirk of PLX switches is that their upstream bridge port has
256K of space allocated behind its BAR0 (most other bridge
implementations do not report any BAR space). The lspci for such device
looks like:
04:00.0 PCI bridge: PLX Technology, Inc. PEX 8724 24-Lane, 6-Port PCI
E
On 4/22/19 3:58 PM, Bjorn Helgaas wrote:
On Fri, Feb 08, 2019 at 10:24:11AM -0600, Alexandru Gagniuc wrote:
This is only used within drivers/pci, and there is no reason to make
it available outside of the PCI core.
Signed-off-by: Alexandru Gagniuc
Applied the whole series to pci/hotplug for
On Mon, 22 Apr 2019 15:57:27 -0700 Kees Cook wrote:
> Commit eab09532d400 ("binfmt_elf: use ELF_ET_DYN_BASE only for PIE"),
> made changes in the rare case when the ELF loader was directly invoked
> (e.g to set a non-inheritable LD_LIBRARY_PATH, testing new versions of
> the loader), by moving in
Hi Vincent,
> On Apr 17, 2019, at 5:56 AM, Vincent Guittot
> wrote:
>
> On Wed, 10 Apr 2019 at 21:43, Song Liu wrote:
>>
>> Hi Morten,
>>
>>> On Apr 10, 2019, at 4:59 AM, Morten Rasmussen
>>> wrote:
>>>
>
>>>
>>> The bit that isn't clear to me, is _why_ adding idle cycles helps your
>>>
Hi Linus and Al...
I just wanted Al to know I tested his patch and acked it and that it
there would be
a conflict if our pagecache code got pulled... I wasn't suggesting that I
should get that one part of Al's patch pulled...
>> I can easily handle any trivial conflicts this causes...
Thanks :-)
On Mon, Apr 22, 2019 at 02:56:57PM -0700, Linus Torvalds wrote:
> On Mon, Apr 22, 2019 at 2:14 PM Mike Marshall wrote:
> >
> > I applied your "new inode method: ->free_inode()" and
> > "orangefs: make use of ->free_inode()" to our pagecache
> > branch (I hope to get it pulled in the next merge win
1 - 100 of 579 matches
Mail list logo
