On Wed, Sep 18, 2019 at 07:00:30PM +0100, Catalin Marinas wrote:
> On Wed, Sep 18, 2019 at 05:00:27PM +0300, Kirill A. Shutemov wrote:
> > On Wed, Sep 18, 2019 at 09:19:14PM +0800, Jia He wrote:
> > > @@ -2152,20 +2163,34 @@ static inline void cow_user_page(struct page
> > > *dst, struct page *src
On Mon, Sep 16, 2019 at 4:11 PM Marcel Ziswiler wrote:
>
> From: Marcel Ziswiler
>
> This patch adds the device tree to support Toradex Colibri iMX8X a
> computer on module which can be used on different carrier boards.
>
> The module consists of a NXP i.MX 8X family SoC (either i.MX 8DualX or
>
Hi all,
Today's linux-next merge of the nvdimm tree got a conflict in:
drivers/nvdimm/pfn_devs.c
between commit:
274b924088e935 ("libnvdimm/pfn: Fix namespace creation on misaligned
addresses")
from the libnvdimm-fixes tree and commit:
edbb52c24441ab ("libnvdimm/pfn_dev: Add page size
Hi Kirill
Thanks for the detailed explanation.
--
Cheers,
Justin (Jia He)
> -Original Message-
> From: Kirill A. Shutemov
> Sent: 2019年9月19日 22:58
> To: Jia He
> Cc: Justin He (Arm Technology China) ; Catalin
> Marinas ; Will Deacon ; Mark
> Rutland ; James Morse
> ; Marc Zyngier ; Ma
On 9/11/19 11:58 AM, Codrin Ciubotariu wrote:
After a transfer timeout, some faulty I2C slave devices might hold down
the SCL or the SDA pins. We can generate a bus clear command, hoping that
the slave might release the pins.
Signed-off-by: Codrin Ciubotariu
---
drivers/i2c/busses/i2c-at91-ma
Hello!
On 09/19/2019 03:29 PM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> The region resource in struct stfsm is unused and can be removed.
OK, except it's not a variable (as the subject says), it's a structure field.
"region resource" also seems strange...
>
> Signed-off-
Replace the syscall entry work handling with the generic version, Provide
the necessary helper inlines to handle the real architecture specific
parts, e.g. audit and seccomp invocations.
Signed-off-by: Thomas Gleixner
---
arch/x86/Kconfig|1
arch/x86/entry/common.c
Replace the syscall entry work handling with the generic version, Provide
the necessary helper inlines to handle the real architecture specific
parts, e.g. audit and seccomp invocations.
Signed-off-by: Thomas Gleixner
---
arch/arm64/Kconfig|1
arch/arm64/include/asm/entr
Evaluating _TIF_NOHZ to decide whether to use the slow syscall entry path
is not only pointless, it's actually counterproductive:
1) Context tracking code is invoked unconditionally before that flag is
evaluated.
2) If the flag is set the slow path is invoked for nothing due to #1
Remove i
To prepare for converting the exit to usermode code to the generic version,
move the irqflags tracing into C code.
Signed-off-by: Thomas Gleixner
---
arch/x86/entry/common.c | 10 ++
arch/x86/entry/entry_32.S| 11 +--
arch/x86/entry/entry_64.S| 10 +
Entering a guest is similar to exiting to user space. Pending work like
handling signals, rescheduling, task work etc. needs to be handled before
that.
Provide generic infrastructure to avoid duplication of the same handling code
all over the place.
Update ARM64 struct kvm_vcpu_stat with a signal
Restoring the FPU is not required to be insided the loop. The final point
to do that is before returning to user space. Move it there.
Signed-off-by: Thomas Gleixner
---
arch/arm64/include/asm/entry-common.h |9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
--- a/arch/arm64/incl
On Mon, Jul 08, 2019 at 09:58:16AM +0200, Auger Eric wrote:
> > + ret = pci_enable_pasid(pdev, features);
> > + if (!ret)
> > + master->ssid_bits = min_t(u8, ilog2(num_pasids),
> > + master->smmu->ssid_bits);
> I don't really get why this setting is
Provide a generic facility to handle the exit to usermode work. That's
aimed to replace the pointlessly different copies in each architecture.
Signed-off-by: Thomas Gleixner
---
include/linux/entry-common.h | 105 +++
kernel/entry/common.c| 88 +
Use the generic infrastructure to check for and handle pending work before
entering into guest mode.
Signed-off-by: Thomas Gleixner
---
arch/x86/kvm/x86.c | 17 +
1 file changed, 5 insertions(+), 12 deletions(-)
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -52,6 +52,7
Replace the exit to usermode code with the generic version.
Signed-off-by: Thomas Gleixner
---
arch/arm64/include/asm/entry-common.h | 29 +
arch/arm64/kernel/entry.S | 18 ++---
arch/arm64/kernel/signal.c| 45
Replace the syscall exit handling code with the generic version. That gets
rid of the interrupts disabled check for work flags. That's a non-issue
because the flags are checked with READ_ONCE() in the core and not
reevaluated. That's perfectly fine because the interrupts disabled check is
also just
The syscall handling code has an obscure check of pending work which does a
shortcut before returning to user space. It calls into the exit work code
when the flags at entry time required an entry into the slowpath. That does
not make sense because the underlying work functionality will reevaluate
Similar to syscall entry all architectures have similar and pointlessly
different code to handle pending work before returning from a syscall to
user space.
Provide a generic version.
Signed-off-by: Thomas Gleixner
---
include/linux/entry-common.h | 31
kernel/entry/c
Replace the x86 specific exit to usermode code with the generic
implementation.
Signed-off-by: Thomas Gleixner
---
arch/x86/entry/common.c | 111
arch/x86/entry/entry_32.S |2
arch/x86/entry/entry_64.S |2
arch/x86/i
Replace the x86 variant with the generic version.
Signed-off-by: Thomas Gleixner
---
arch/x86/entry/common.c | 44
arch/x86/include/asm/entry-common.h |2 +
2 files changed, 3 insertions(+), 43 deletions(-)
--- a/arch/x86/entry/common.c
+++
When working on a way to move out the posix cpu timer expiry out of the
timer interrupt context, I noticed that KVM is not handling pending task
work before entering a guest. A quick hack was to add that to the x86 KVM
handling loop. The discussion ended with a request to make this a generic
infras
On syscall entry certain work needs to be done conditionally like tracing,
seccomp etc. This code is duplicated in all architectures.
Provide a generic version.
Signed-off-by: Thomas Gleixner
---
arch/Kconfig |3 +
include/linux/entry-common.h | 122
This driver's remove path calls cancel_delayed_work().
However, that function does not wait until the work function
finishes. This could mean that the work function is still
running after the driver's remove function has finished,
which would result in a use-after-free.
Fix by calling cancel_delay
On 09/19/19 16:37, Vincent Guittot wrote:
> On Thu, 19 Sep 2019 at 16:32, Vincent Guittot
> wrote:
> >
> > On Thu, 19 Sep 2019 at 16:23, Qais Yousef wrote:
> > >
> > > On 09/19/19 14:27, Vincent Guittot wrote:
> > > > > > > But for requirement of performance, I think it is better to
> > > > > >
On 9/19/2019 9:15 AM, Matthew Wilcox wrote:
> Why is it organised this way? I mean, yes, technically, rxrpc is a
> generic layer-6 protocol that any blah blah blah, but in practice no
> other user has come up in the last 37 years, so why bother pretending
> one is going to? Just git mv net/rxrpc
Hi Mark,
On Wed, Sep 19, 2019 at 14:31:32AM +0100, Mark Brown wrote:
> On Wed, Sep 18, 2019 at 09:04:32AM +0100, Gareth Williams wrote:
>
> > Gareth Williams (1):
> > dt-bindings: snps,dw-apb-ssi: Add optional clock domain information
> >
> > Phil Edworthy (3):
> > dt: spi: Add Renesas RZ/N1
On Thu, 19 Sep 2019, Greg KH wrote:
> On Thu, Sep 19, 2019 at 05:18:15PM +0800, Xiaoming Ni wrote:
> > Using kzalloc() to allocate memory in function con_init(), but not
> > checking the return value, there is a risk of null pointer references
> > oops.
> >
> > Signed-off-by: Xiaoming Ni
>
>
Le 18/09/2019 à 15:42, Michael Ellerman a écrit :
Hi Laurent,
Few comments ...
Hi Michael,
Thanks for the review and the nitpicking ;)
Laurent Dufour writes:
Now we do not call _BLOCK_REMOVE all the time when the feature is
exhibited.
This isn't true until after the patch is applied, ie
On Wed, Sep 18, 2019 at 8:57 PM Alan Stern wrote:
>
> On Tue, 17 Sep 2019, syzbot wrote:
>
> > Hello,
> >
> > syzbot has tested the proposed patch but the reproducer still triggered
> > crash:
> > WARNING in sysfs_remove_group
> >
> > [ cut here ]
> > sysfs group 'power' no
Hi Philipp,
see below...
On Thu, 2019-09-19 at 16:29 +0200, Philipp Puschmann wrote:
> For some years and since many kernel versions there are reports that the
> RX UART SDMA channel stops working at some point. The workaround was to
> disable DMA for RX. This commit tries to fix the problem itse
On Thu, Sep 19, 2019 at 7:34 AM Theodore Y. Ts'o wrote:
>
> > It's basically a "we used up entropy" thing, which is very
> > questionable to begin with as the whole discussion has shown, but
> > since it stops doing it after 10 cases, it's not even good security
> > assuming the "use up entropy" c
On Thu, Sep 19, 2019 at 03:14:54PM +, Gareth Williams wrote:
> On Wed, Sep 19, 2019 at 14:31:32AM +0100, Mark Brown wrote:
> > Please use subject lines matching the style for the subsystem. This makes
> > it
> > easier for people to identify relevant patches. This isn't even consistent
> >
On Thu, Sep 19, 2019 at 8:02 AM Mark Brown wrote:
>
> Hi all,
>
> Today's linux-next merge of the nvdimm tree got a conflict in:
>
> drivers/nvdimm/pfn_devs.c
>
> between commit:
>
> 274b924088e935 ("libnvdimm/pfn: Fix namespace creation on misaligned
> addresses")
>
> from the libnvdimm-fixe
+ trans_pcie->rba.alloc_wq = alloc_workqueue("rb_allocator",
+ WQ_HIGHPRI | WQ_UNBOUND, 1);
+ if (!trans_pcie->rba.alloc_wq) {
I would like to stick to if(unlikely(!trans_pcie->rba.alloc_wq) just
for consistency.
That's just
The experimental root file system support in cifs.ko relies on
ipconfig to set up the network stack and then accessing the SMB share
that contains the rootfs files.
Cc: "David S. Miller"
Cc: Alexey Kuznetsov
Cc: Hideaki YOSHIFUJI
Signed-off-by: Paulo Alcantara (SUSE)
---
net/ipv4/ipconfig.c |
Add a new virtual device named /dev/cifs (0xfe) to tell the kernel to
mount the root file system over the network by using SMB protocol.
cifs_root_data() will be responsible to retrieve the parsed
information of the new command-line option (cifsroot=) and then call
do_mount_root() with the appropr
Introduce a new CONFIG_CIFS_ROOT option to handle root file systems
over a SMB share.
In order to mount the root file system during the init process, make
cifs.ko perform non-blocking socket operations while mounting and
accessing it.
Signed-off-by: Paulo Alcantara (SUSE)
Signed-off-by: Aurelien
The following are dts patches to add MMC/SD Support on TI's J721e base
board.
Patches depend on Lokesh's gpio patches[1] and device exclusivity patches[2].
[1] https://patchwork.kernel.org/cover/11085643/
[2] https://patchwork.kernel.org/cover/11051559/
Faiz Abbas (2):
arm64: dts: ti: j721e-ma
Add nodes for the 3 SDHCI instances present on TI's J721E device.
instance 0 supports HS400 (8 bit bus widht, DDR, 400 MBps)
while instances 1 and 2 support SDR104 (4 bit width, SDR, 100 MBps) as
their highest speed modes. Currently, only High speed (50 MHz clock) has
been enabled.
Signed-off-by:
sdhci0 is connected to an eMMC and sdhci1 is connected to an SD card
slot. Add support for these nodes.
Signed-off-by: Faiz Abbas
---
.../dts/ti/k3-j721e-common-proc-board.dts | 34 +++
1 file changed, 34 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-j721e-common-proc
Even when using a gpio as chip select, the registers controlling the
hardware chip select have to be configured. However any of the 4
hardware CS can be controlled.
Until now, the gpio index was used to match an hardware chip select,
which limited the number of CS than can be used. Using more than
From: Markus Elfring
Date: Thu, 19 Sep 2019 17:27:57 +0200
Simplify this function implementation by using a known wrapper function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
sound/soc/xilinx/xlnx_formatter_pcm.c | 9 +
1 file changed,
AV32 support has been from the kernel a few release ago, but there was
still some specific macro for this architecture in this driver. Lets
remove it.
Signed-off-by: Gregory CLEMENT
---
drivers/spi/spi-atmel.c | 24
1 file changed, 24 deletions(-)
diff --git a/drivers/s
On Thu, Sep 19, 2019 at 06:00:07PM +0300, Kirill A. Shutemov wrote:
> On Wed, Sep 18, 2019 at 07:00:30PM +0100, Catalin Marinas wrote:
> > On Wed, Sep 18, 2019 at 05:00:27PM +0300, Kirill A. Shutemov wrote:
> > > On Wed, Sep 18, 2019 at 09:19:14PM +0800, Jia He wrote:
> > > > @@ -2152,20 +2163,34 @
On 19/09/19 17:03, Thomas Gleixner wrote:
> Use the generic infrastructure to check for and handle pending work before
> entering into guest mode.
>
> Signed-off-by: Thomas Gleixner
Subject should be "x86/kvm: use exit_to_guestmode".
Paolo
> ---
> arch/x86/kvm/x86.c | 17 +
>
Quick API review before I dive into the implementation.
On 19/09/19 17:03, Thomas Gleixner wrote:
> + /*
> + * Before returning to guest mode handle all pending work
> + */
> + if (ti_work & _TIF_SIGPENDING) {
> + vcpu->run->exit_reason = KVM_EXIT_INTR;
> +
On Thu, Sep 19, 2019 at 09:08:11PM +0800, Jason Wang wrote:
> On 2019/9/18 下午10:32, Michael S. Tsirkin wrote:
> > > > > So I have some questions:
> > > > >
> > > > > 1) Compared to method 2, what's the advantage of creating a new vhost
> > > > > char
> > > > > device? I guess it's for keep the AP
In adis_update_scan_mode, if allocation for adis->buffer fails,
previously allocated adis->xfer needs to be released.
v2: added adis->xfer = NULL to avoid any potential double free.
Signed-off-by: Navid Emamdoost
---
drivers/iio/imu/adis_buffer.c | 5 -
1 file changed, 4 insertions(+), 1 de
On Thu, Sep 19, 2019 at 8:20 AM Linus Torvalds
wrote:
>
> The silly "reset crng_init_cnt" does absolutely nothing to help that,
> but in fact what it does is to basically give the attacker a way to
> get an infinite stream of data without any reseeding (because that
> only happens after crng_read(
> I have been investigating a regression in our environment where pstore
> (efi-pstore specifically but I suspect this would affect all
> implementations) no longer works after upgrading from a 4.4 to 5.0
> kernel when running under xen. (This is an Ubuntu kernel but I don't
> think there are
On Thu, Sep 19, 2019 at 03:41:43PM +, Catalin Marinas wrote:
> On Thu, Sep 19, 2019 at 06:00:07PM +0300, Kirill A. Shutemov wrote:
> > On Wed, Sep 18, 2019 at 07:00:30PM +0100, Catalin Marinas wrote:
> > > On Wed, Sep 18, 2019 at 05:00:27PM +0300, Kirill A. Shutemov wrote:
> > > > On Wed, Sep 1
The following commit has been merged into the timers/urgent branch of tip:
Commit-ID: e430d802d6a3aaf61bd3ed03d9404888a29b9bf9
Gitweb:
https://git.kernel.org/tip/e430d802d6a3aaf61bd3ed03d9404888a29b9bf9
Author:Li RongQing
AuthorDate:Thu, 19 Sep 2019 20:04:47 +08:00
Committ
Linus,
Please pull Devicetree updates for 5.4.
Rob
The following changes since commit 83f82d7a42583e93d0f0dde3d61ed10f75c0f4d8:
of: irq: fix a trivial typo in a doc comment (2019-08-14 20:12:16 -0600)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/r
On 09/19/2019 05:33 PM, Vignesh Raghavendra wrote:
> Hi Tudor
>
Hi, Vignesh,
> [...]
>
> On 17-Sep-19 9:25 PM, tudor.amba...@microchip.com wrote:
>> +static int spi_nor_write_16bit_sr_and_check(struct spi_nor *nor, u8
>> status_new,
>> +u8 mask)
>> +{
In adis_update_scan_mode_burst, if adis->buffer allocation fails release
the adis->xfer.
v2: set adis->xfer = NULL to avoid any potential double free.
Signed-off-by: Navid Emamdoost
---
drivers/iio/imu/adis_buffer.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers
>> +/*
>> + * cna_try_find_next - scan the main waiting queue looking for the first
>> + * thread running on the same NUMA node as the lock holder. If found (call
>> it
>> + * thread T), move all threads in the main queue between the lock holder and
>> + * T to the end of the secondary queue and r
Le 18/09/2019 à 15:42, Michael Ellerman a écrit :
Hi Laurent,
Comments below ...
Hi Michael,
Thanks for your review.
One comment below (at the end).
Laurent Dufour writes:
The PAPR document specifies the TLB Block Invalidate Characteristics which
tells for each couple segment base page
On Thu, Sep 19, 2019 at 6:59 AM David Howells wrote:
>
> But I don't agree with this. You're missing half the barriers. There should
> be *four* barriers. The document mandates only 3 barriers, and uses
> READ_ONCE() where the fourth should be, i.e.:
>
>thread #1thread #2
>
>
The following changes since commit d1abaeb3be7b5fa6d7a1fbbd2e14e3310005c4c1:
Linux 5.3-rc5 (2019-08-18 14:31:08 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/danielt/linux.git/
tags/kgdb-5.4-rc1
for you to fetch changes up to d8a050f5a3e824224
On Thu, Sep 19, 2019 at 05:38:47PM +0200, Gregory CLEMENT wrote:
> With this patch, when using a gpio CS, the hardware CS0 is always
> used. Thanks to this, there is no more limitation for the number of
> gpio CS we can use.
This is going to break any system where we use both a GPIO chip select
a
It's very often for embedded to have stripped version of sort in
busybox, when no -V option present. It breaks build natively on target
board causing recursive loop.
BusyBox v1.24.1 (2019-04-06 04:09:16 UTC) multi-call binary. \
Usage: sort [-nrugMcszbdfimSTokt] [-o FILE] [-k \
start[.offset][opts
Hi all,
Changes since 20190918:
The btrfs-kave tree gained a conflict with Linus' tree which I wasn't
comfortable resolving so I skipped the tre for today.
The ext4 tree gained a conflict with Linus' tree which I fixed up.
The nvdimm tree gained a conflict with the libnvdimm-fixes tree which I
On 09/19/2019 05:37 PM, Vignesh Raghavendra wrote:
> External E-Mail
>
>
> Hi,
Hi, thanks for reviewing!
>
> On 17-Sep-19 9:24 PM, tudor.amba...@microchip.com wrote:
>> From: Tudor Ambarus
>>
> [...]
>> Tudor Ambarus (23):
>> mtd: spi-nor: hisi-sfc: Drop nor->erase NULL assignment
>> mt
The following changes since commit 5c6207539aea8b22490f9569db5aa72ddfd0d486:
Merge branch 'fixes' of
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2019-07-31 13:26:54
-0700)
are available in the Git repository at:
https://github.com/cminyard/linux-ipmi.git tags/for-linus-5.4-1
f
We're missing a depends in the Kconfig, which can lead to trying to
build without the required headers being present..
HOSTCC samples/watch_queue/watch_test
samples/watch_queue/watch_test.c:23:10: fatal error: linux/watch_queue.h: No
such file or directory
23 | #include
| ^~
When we tested pmdk unit test vmmalloc_fork TEST1 in arm64 guest, there
will be a double page fault in __copy_from_user_inatomic of cow_user_page.
As told by Catalin: "On arm64 without hardware Access Flag, copying from
user will fail because the pte is old and cannot be marked young. So we
always
We unconditionally set the HW_AFDBM capability and only enable it on
CPUs which really have the feature. But sometimes we need to know
whether this cpu has the capability of HW AF. So decouple AF from
DBM by new helper cpu_has_hw_af().
Reported-by: kbuild test robot
Suggested-by: Suzuki Poulose
When we tested pmdk unit test [1] vmmalloc_fork TEST1 in arm64 guest, there
will be a double page fault in __copy_from_user_inatomic of cow_user_page.
Below call trace is from arm64 do_page_fault for debugging purpose
[ 110.016195] Call trace:
[ 110.016826] do_page_fault+0x5a4/0x690
[ 110.0178
On arm64 without hardware Access Flag, copying fromuser will fail because
the pte is old and cannot be marked young. So we always end up with zeroed
page after fork() + CoW for pfn mappings. we don't always have a
hardware-managed access flag on arm64.
Hence implement arch_faults_on_old_pte on arm
On Thu, Sep 19, 2019 at 03:51:33PM +, Luck, Tony wrote:
> > I have been investigating a regression in our environment where pstore
> > (efi-pstore specifically but I suspect this would affect all
> > implementations) no longer works after upgrading from a 4.4 to 5.0
> > kernel when running u
Hi Rishi,
On Wed, Sep 18, 2019 at 09:59:11PM +0530, Rishi Gupta wrote:
> This commit replaces direct invocations of printk with
> their appropriate pr_info/warn() variant.
>
> Signed-off-by: Rishi Gupta
> ---
> Changes in v2:
> - Removed manually adding prefix "hidraw:".
>
> drivers/hid/hidraw
Hi Dexuan,
On Wed, Sep 11, 2019 at 11:36:20PM +, Dexuan Cui wrote:
> We need hv_kbd_pm_notify() to make sure the pm_wakeup_hard_event() call
> does not prevent the system from entering hibernation: the hibernation
> is a relatively long process, which can be aborted by the call
> pm_wakeup_har
Thermal framework takes 0 as the lowest/default state for a
cooling/warming device. The current code has the order reverted with
1 corresponding to lowest state in hardware and 0 the highest state.
Invert this for a better fit with the thermal framework.
Signed-off-by: Thara Gopinath
---
drivers
On Thu, Sep 19, 2019 at 10:39:18PM +0900, Suleiman Souhlal wrote:
> On Fri, Sep 6, 2019 at 6:57 AM Roman Gushchin wrote:
> > The patchset has been tested on a number of different workloads in our
> > production. In all cases, it saved hefty amounts of memory:
> > 1) web frontend, 650-700 Mb, ~42%
Hi.
Recently, I've got the following card:
01:00.0 Network controller: MEDIATEK Corp. Device 7612
Subsystem: MEDIATEK Corp. Device 7612
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at 8120 (64-bit, non-prefetchable) [size=1M]
Expansion ROM at 81300
On 19.09.2019 18:06, kbouhara wrote:
>
> On 9/11/19 11:58 AM, Codrin Ciubotariu wrote:
>> After a transfer timeout, some faulty I2C slave devices might hold down
>> the SCL or the SDA pins. We can generate a bus clear command, hoping that
>> the slave might release the pins.
>>
>> Signed-off-by: C
Hi Mathieu,
Sorry for the delay in responding.
On Fri, Sep 13, 2019 at 10:22:28AM -0400, Mathieu Desnoyers wrote:
> - On Sep 12, 2019, at 11:47 AM, Will Deacon w...@kernel.org wrote:
>
> > On Thu, Sep 12, 2019 at 03:24:35PM +0100, Linus Torvalds wrote:
> >> On Thu, Sep 12, 2019 at 2:48 PM Wi
On Wed 18 Sep 2019 at 14:36, Qianggui Song wrote:
> On 2019/9/17 22:07, Jerome Brunet wrote:
>>
>> On Tue 17 Sep 2019 at 13:51, Qianggui Song wrote:
> diff --git a/drivers/pinctrl/meson/pinctrl-meson.c
> b/drivers/pinctrl/meson/pinctrl-meson.c
> index 8bba9d0..885b89d 100644
>
On 9/19/19 1:37 AM, Parth Shah wrote:
>
>>
>> $> Separating AVX512 tasks and latency sensitive tasks on separate cores
>> -
>> Another usecase we are considering is to segregate those workload that will
>> pull down
>> core c
On Thu, Sep 19, 2019 at 2:49 AM David Howells wrote:
>
> Actually, waiting for all outstanding fixes to get merged and then rebasing
> might not be the right thing here. The problem is that there are fixes in
> both trees: afs fixes go directly into yours whereas rxrpc fixes go via
> networking a
On 9/19/19 2:06 AM, David Laight wrote:
> From: Tim Chen
>> Sent: 18 September 2019 18:16
> ...
>> Some users are running machine learning batch tasks with AVX512, and have
>> observed
>> that these tasks affect the tasks needing a fast response. They have to
>> rely on manual CPU affinity to sep
On Thu, Sep 19, 2019 at 10:52:35AM +, Jerome Pouiller wrote:
> +static int wfx_sdio_copy_from_io(void *priv, unsigned int reg_id,
> + void *dst, size_t count)
> +{
> + struct wfx_sdio_priv *bus = priv;
> + unsigned int sdio_addr = reg_id << 2;
> + int re
Hi Linus,
These are the proposed RDMA patches for 5.4
This cycle has proved to be quiet with a focus on bug fix and cleanup style
patches, and less on major new functionality. I am aware of no conflicts.
The following changes since commit f74c2bb98776e2de508f4d607cd519873065118e:
Linux 5.3-rc
On Wed, 18 Sep 2019 12:15:37 -0700
Matthias Kaehlcke wrote:
> Add a tracepoint for frequency changes of devfreq devices and
> use it.
>
> Signed-off-by: Matthias Kaehlcke
> ---
> drivers/devfreq/devfreq.c | 3 +++
> include/trace/events/devfreq.h | 18 ++
> 2 files change
On Fri, Sep 20, 2019 at 12:12:02AM +0800, Jia He wrote:
> diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
> index b1fdc486aed8..fb0e9425d286 100644
> --- a/arch/arm64/kernel/cpufeature.c
> +++ b/arch/arm64/kernel/cpufeature.c
> @@ -1141,6 +1141,16 @@ static bool has_hw_
On 9/19/19 12:14 PM, James Dingwall wrote:
> On Thu, Sep 19, 2019 at 03:51:33PM +, Luck, Tony wrote:
>>> I have been investigating a regression in our environment where pstore
>>> (efi-pstore specifically but I suspect this would affect all
>>> implementations) no longer works after upgrading
On Thu, Sep 19, 2019 at 06:34:29PM +0200, Andrew Lunn wrote:
> On Thu, Sep 19, 2019 at 10:52:35AM +, Jerome Pouiller wrote:
> > +static int wfx_sdio_copy_from_io(void *priv, unsigned int reg_id,
> > +void *dst, size_t count)
> > +{
> > + struct wfx_sdio_priv *bus =
On 9/18/19 9:12 PM, Valentin Schneider wrote:
> On 18/09/2019 15:18, Patrick Bellasi wrote:
>>> 1. Name: What should be the name for such attr for all the possible
>>> usecases?
>>> =
>>> Latency nice is the proposed name as of now where the lower value indicates
>>> that the task d
On Fri, Sep 20, 2019 at 12:12:04AM +0800, Jia He wrote:
> @@ -2152,7 +2163,29 @@ static inline void cow_user_page(struct page *dst,
> struct page *src, unsigned lo
>*/
> if (unlikely(!src)) {
> void *kaddr = kmap_atomic(dst);
> - void __user *uaddr = (void _
On 18/09/2019 18:19, Bjorn Andersson wrote:
Fixes for issues found in GLINK during reboot testing of a remoteproc.
Arun Kumar Neelakantam (2):
rpmsg: glink: Fix reuse intents memory leak issue
rpmsg: glink: Fix use after free in open_ack TIMEOUT case
Bjorn Andersson (2):
rpmsg: glin
On Wed, Sep 18, 2019 at 09:04:21PM -0700, Randy Dunlap wrote:
> On 9/18/19 3:10 PM, Mark Brown wrote:
> > Hi all,
> >
> > Changes since 20190917:
> >
>
> on x86_64:
>
> drivers/gpu/drm/i915/gem/i915_gem_execbuffer.o: warning: objtool:
> i915_gem_execbuffer2_ioctl()+0x2fb: call to gen8_canonica
Dear Friend,
My Name is Mr Yakubu Nelson, I have been searching for your
contact since you left our country some years ago .I do not know
whether this is your correct email address or not because I only used
your name initials to search for your contact in the internet .In case
you are not the per
On Thu, Sep 19, 2019 at 01:42:51PM +0300, Dmitry V. Levin wrote:
> On Wed, Sep 18, 2019 at 10:33:09AM -0700, Kees Cook wrote:
> > This is actually fixed in -next already (and, yes, with the Fixes line
> > Tyler has mentioned):
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kse
On 9/19/19 10:55 AM, Kees Cook wrote:
On Thu, Sep 19, 2019 at 01:42:51PM +0300, Dmitry V. Levin wrote:
On Wed, Sep 18, 2019 at 10:33:09AM -0700, Kees Cook wrote:
This is actually fixed in -next already (and, yes, with the Fixes line
Tyler has mentioned):
https://git.kernel.org/pub/scm/linux/ke
-Original Message-
From: Nikolaus Voss [mailto:n...@vosn.de]
Sent: Wednesday, September 18, 2019 7:32 AM
To: Moore, Robert
Cc: Ferry Toth ; Shevchenko, Andriy
; Schmauss, Erik ; Rafael
J. Wysocki ; Len Brown ; Jacek Anaszewski
; Pavel Machek ; Dan Murphy
; linux-a...@vger.kernel.or
Quoting Jerome Brunet (2019-09-19 06:01:28)
> On Thu 19 Sep 2019 at 11:38, Neil Armstrong wrote:
>
> > Make sure we always enable a PLL on a set_rate() when the PLL is
> > flagged as critical.
> >
> > This fixes the case when the Amlogic G12A SYS_PLL gets disabled by the
> > PSCI firmware when re
On Tue, Sep 17, 2019 at 8:24 PM Alan Stern wrote:
>
> On Mon, 16 Sep 2019, syzbot wrote:
>
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
> > git tree: https://github.com/google/kasan.git usb-fuzzer
> > conso
Please pull the following changes since commit
4d856f72c10ecb060868ed10ff1b1453943fc6c8:
Linux 5.3 (2019-09-15 14:19:32 -0700)
are available in the Git repository at:
git://git.samba.org/sfrench/cifs-2.6.git tags/5.4-smb3-fixes
for you to fetch changes up to 4d6bcba70aeb4a512ead9c9eaf9edc6b
On Wed, Sep 18, 2019 at 05:05:26PM +0200, Dmitry Vyukov wrote:
> On Wed, Sep 18, 2019 at 1:19 PM syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:a7f89616 Merge branch 'for-5.3-fixes' of git://git.kernel...
> > git tree: upstream
> > console
401 - 500 of 1297 matches
Mail list logo
