On 16 October 2020 22:23:46 BST, Jens Axboe wrote:
>Hi,
>
>Ran into this one yesterday:
>
>drivers/iommu/intel/dmar.c: In function ‘free_iommu’:
>drivers/iommu/intel/dmar.c:1139:41: error: ‘struct iommu_device’ has no
>member named ‘ops’
> 1139 | if (intel_iommu_enabled && iommu->iommu.ops) {
From: Patrick Stählin
Needed for kprobes support. Copied and adapted from arm64 code.
Guo Ren fixup pt_regs type for linux-5.8-rc1.
Signed-off-by: Patrick Stählin
Signed-off-by: Guo Ren
Reviewed-by: Pekka Enberg
Reviewed-by: Zong Li
Reviewed-by: Masami Hiramatsu
---
arch/riscv/Kconfig
From: Guo Ren
The patchset includes kprobe/uprobe support and some related fixups.
Patrick provides HAVE_REGS_AND_STACK_ACCESS_API support and some
kprobe's code. The framework of k/uprobe is from csky but also refers
to other arches'. kprobes on ftrace is also supported in the patchset.
Modify d
From: Guo Ren
This patch adds support for uprobes on riscv architecture.
Just like kprobe, it support single-step and simulate instructions.
Signed-off-by: Guo Ren
Reviewed-by: Pekka Enberg
Cc: Oleg Nesterov
Cc: Masami Hiramatsu
Cc: Palmer Dabbelt
---
arch/riscv/Kconfig
From: Guo Ren
Unfortunately, the current code couldn't be compiled:
CC arch/riscv/kernel/patch.o
In file included from ./include/linux/kernel.h:11,
from ./include/linux/list.h:9,
from ./include/linux/preempt.h:11,
from ./include/linux/spi
From: Guo Ren
Inspired by the commit 42d038c4fb00 ("arm64: Add support for function
error injection"), this patch supports function error injection for
riscv.
This patch mainly support two functions: one is regs_set_return_value()
which is used to overwrite the return value; the another function
From: Guo Ren
This patch adds support for kprobes on ftrace call sites to avoids
much of the overhead with regular kprobes. Try it with simple
steps:
1. Get _do_fork ftrace call site.
Dump of assembler code for function _do_fork:
0xffe00020af64 <+0>: addisp,sp,-128
0xffe000
From: Guo Ren
This patch enables "kprobe & kretprobe" to work with ftrace
interface. It utilized software breakpoint as single-step
mechanism.
Some instructions which can't be single-step executed must be
simulated in kernel execution slot, such as: branch, jal, auipc,
la ...
Some instructions
From: Guo Ren
We must use $(CC_FLAGS_FTRACE) instead of directly using -pg. It
will cause -fpatchable-function-entry error.
Signed-off-by: Guo Ren
---
arch/riscv/kernel/Makefile | 4 ++--
arch/riscv/mm/Makefile | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/ris
From: Guo Ren
This patch changes the current detour mechanism of dynamic ftrace
which has been discussed during LPC 2020 RISCV-MC [1].
Before the patch, we used mcount for detour:
:
addi sp,sp,-16
sd ra,8(sp)
sd s0,0(sp)
addi s0,sp,16
mv a5,ra
From: Guo Ren
It will cause warning messages:
echo function_graph > /sys/kernel/debug/tracing/current_tracer
[ 47.691397] [ cut here ]
[ 47.692899] WARNING: CPU: 0 PID: 11 at arch/riscv/kernel/patch.c:63
patch_insn_write+0x182/0x19a
[ 47.694483] Modules linked in:
[
Hi Jagan.
On Fri, Sep 04, 2020 at 11:38:19PM +0530, Jagan Teki wrote:
> Add vendor dt-bindings for Yes Optoelectronics Co.,Ltd.
>
> Signed-off-by: Jagan Teki
I have applied the full series to drm-misc-next.
Sorry for the delay.
Sam
> ---
> Documentation/devicetree/bindings/vendor-pre
On Fri, 16 Oct 2020 at 14:41, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.4.72 release.
> There are 22 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Resp
On Sat, Oct 17, 2020 at 08:55:34AM +0200, Jann Horn wrote:
> My suggestion is to use a counter *in the UAPI*, not in the hypervisor
> protocol. (And as long as that counter can only miss increments in a
> cryptographically negligible fraction of cases, everything's fine.)
OK I got it now and I agr
Hi Allen
On Fri, Sep 04, 2020 at 10:10:23AM +0800, allen wrote:
> This adds support for the iTE IT6505.
> This device can convert DPI signal to DP output.
>
> From: Allen Chen
> Signed-off-by: Jitao Shi
> Signed-off-by: Pi-Hsun Shih
> Signed-off-by: Yilun Lin
> Signed-off-by: Hermes Wu
> Sig
On Sat, 2020-10-17 at 11:32 +0530, Dwaipayan Ray wrote:
> > Why include a + character here?
> >
> Hi,
> I tried it without + first, but then lines like
> "The the repeated word."
> didn't register a warning.
>
> I think checkpatch adds a + to the line when used on
> files. Am not sure but my $raw
On Fri, 16 Oct 2020 at 14:40, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.152 release.
> There are 21 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Re
a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Hemant-Kumar/userspace-MHI-client-interface-driver/20201017-140145
base: https://git.kernel.org/pub/scm/linux/
> Am 17.10.2020 um 04:03 schrieb Sudarshan Rajagopalan
> :
>
> On receiving the MEM_GOING_OFFLINE notification, we disallow offlining of
> any boot memory by checking if section_early or not. With the introduction
> of SECTION_MARK_HOTPLUGGABLE, allow boot mem sections that are marked as
> hot
We have introduced helper function bio_copy_dev. Just use it.
Signed-off-by: Jeff Xie
---
block/bio.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/block/bio.c b/block/bio.c
index 640d0fb..9fce7df 100644
--- a/block/bio.c
+++ b/block/bio.c
@@ -679,8 +679,6 @@ void __bio_
> Am 17.10.2020 um 00:38 schrieb Wei Yang :
>
> On Fri, Oct 16, 2020 at 12:32:50PM +0200, David Hildenbrand wrote:
> Ok, I seems to understand the logic now.
>
> But how we prevent ONLINE_PARTIAL memory block get offlined? There are
> three
> calls in virtio_mem_set_fake_o
On Sat, Oct 17, 2020 at 3:33 AM Andrey Konovalov wrote:
>
> Now that we have KASAN-KUNIT tests integration, it's easy to see that
> some KASAN tests are not adopted to the SW_TAGS mode and are failing.
>
> Adjust the allocation size for kasan_memchr() and kasan_memcmp() by
> roung it up to OOB_TAG
On Fri, 16 Oct 2020 at 14:39, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.202 release.
> There are 18 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Re
Recently, commit 4f6ad8aa1eac ("checkpatch: move repeated word test")
moved the repeated word test to check for more file types. But after
this, if checkpatch.pl is run on MAINTAINERS, it generates several
new warnings of the type:
WARNING: Possible repeated word: 'git'
For example:
WARNING: Poss
On Fri, 16 Oct 2020 at 14:38, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.240 release.
> There are 16 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Res
Hi Krzysztof
On Thu, Aug 27, 2020 at 09:11:06AM +0200, Krzysztof Kozlowski wrote:
> platform_get_irq() returns -ERRNO on error. In such case comparison
> to 0 would pass the check.
>
> Fixes: 5fc537bfd000 ("drm/mcde: Add new driver for ST-Ericsson MCDE")
> Signed-off-by: Krzysztof Kozlowski
Th
Hello Linus,
I'm a bit late, but here is the I3C PR for 5.10.
Regards,
Boris
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/i3c/li
Hi Vinay
On Tue, Sep 08, 2020 at 08:57:07PM +0300, Laurent Pinchart wrote:
> Hi Vinay,
>
> On Tue, Sep 08, 2020 at 11:22:48PM +0530, Vinay Simha B N wrote:
> > laurent,
> >
> > Please review or give some feedback.
>
> I'm sorry, I have very little time these days :-( Maybe Neil can provide
> fe
On Sat, 17 Oct 2020 00:49:13 +0200,
Colin King wrote:
>
> From: Colin Ian King
>
> Don't populate const arrays on the stack but instead make them
> static. Makes the object code smaller by 57 bytes.
>
> Before:
>text data bss dec hex filename
> 173256 38016
On Fri, 16 Oct 2020 19:44:05 +0200,
Randy Dunlap wrote:
>
> Change the duplicated word "the" to "Then the".
>
> Signed-off-by: Randy Dunlap
> Cc: Jaroslav Kysela
> Cc: Takashi Iwai
> Cc: alsa-de...@alsa-project.org
> Cc: Joe Perches
> ---
> v2: use "Then the" instead of just "The". (Joe Perch
Hi Lubomir.
Sorry for the late feedback!
On Wed, Aug 19, 2020 at 12:12:06PM +0200, Lubomir Rintel wrote:
> This adds support for the Innolux LS075AT011 7.5" 1200x900 panel. There's
> no public data sheet for the panel -- the values have been taken from Open
> Firmware and the documentation for th
On Fri, 16 Oct 2020 at 14:37, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.4.240 release.
> There are 16 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Res
Hi Bernard.
On Fri, Aug 14, 2020 at 01:30:19AM -0700, Bernard Zhao wrote:
> In function via_mem_alloc`s error branch, DRM_ERROR is protected
> in the mutex_lock(&dev->struct_mutex) area.
> >From the code, we see that DRM_ERROR is just an error log print
> without any struct element, there is no ne
On Fri, Oct 16, 2020 at 03:06:27PM +0200, Pavel Machek wrote:
> Hi!
>
> > From: Anant Thazhemadam
> >
> > commit e1f13c879a7c21bd207dc6242455e8e3a1e88b40 upstream.
> >
> > While finding usb endpoints in vmk80xx_find_usb_endpoints(), check if
> > wMaxPacketSize = 0 for the endpoints found.
> >
On Fri, Oct 16, 2020 at 07:02:23PM -0700, Sudarshan Rajagopalan wrote:
> Certain architectures such as arm64 doesn't allow boot memory to be
> offlined and removed. Distinguish certain memory sections as
> "hotpluggable" which can be marked by module drivers stating to memory
> hotplug layer that t
David Gow writes:
> Add some basic sanity-check tests for the fat_checksum() function and
> the fat_time_unix2fat() and fat_time_fat2unix() functions. These unit
> tests verify these functions return correct output for a number of test
> inputs.
>
> These tests were inspored by -- and serve a sim
Hi Sam,
On Fri, Oct 16, 2020 at 04:29:16PM +0200, Sam Ravnborg wrote:
> Hi Guido.
> On Tue, Oct 13, 2020 at 12:32:45PM +0200, Guido Günther wrote:
[..snip..]
> >
> > Changes from v1:
> > - As per review comments by Fabio Estevam
> >
> > https://lore.kernel.org/dri-devel/CAOMZO5B5ECcConvKej=rc
Hi Folks,
On 10/10/2020 1:31 AM, Sandeep Singh wrote:
From: Sandeep Singh
AMD SFH(Sensor Fusion Hub) is HID based driver.SFH FW is part of MP2
processor (MP2 which is an ARM core connected to x86 for processing
sensor data) and it runs on MP2 where in the driver resides on X86.
The driver func
On 17.10.20 01:11, Sudarshan Rajagopalan wrote:
>
> Hello Anshuman,
>
David here,
in general, if your driver offlines+removes random memory, it is doing
something *very* wrong and dangerous. You shouldn't ever be
offlining+removing memory unless
a) you own that boot memory after boot. E.g., the
On 17.10.20 10:26, Mike Rapoport wrote:
> On Fri, Oct 16, 2020 at 07:02:23PM -0700, Sudarshan Rajagopalan wrote:
>> Certain architectures such as arm64 doesn't allow boot memory to be
>> offlined and removed. Distinguish certain memory sections as
>> "hotpluggable" which can be marked by module dri
hi,
On Fri, Oct 16, 2020 at 12:01:51PM -0700, Guenter Roeck wrote:
> On Fri, Oct 16, 2020 at 11:07:19AM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.19.152 release.
> > There are 21 patches in this series, all will be posted as a response
> > to this
I'm announcing the release of the 4.4.240 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
On Sat, Oct 17, 2020 at 11:41:53AM +0200, Salvatore Bonaccorso wrote:
> hi,
>
> On Fri, Oct 16, 2020 at 12:01:51PM -0700, Guenter Roeck wrote:
> > On Fri, Oct 16, 2020 at 11:07:19AM +0200, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.19.152 release.
> > >
I'm announcing the release of the 4.14.202 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web browser
diff --git a/Makefile b/Makefile
index 82bb1b27d2f5..a6a9d494dc18 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 9
-SUBLEVEL = 239
+SUBLEVEL = 240
EXTRAVERSION =
NAME = Roaring Lionus
diff --git a/drivers/crypto/qat/qat_common/qat_algs.c
b/drivers/crypto/qat/qa
I'm announcing the release of the 4.9.240 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 74072b5a958b..69e7cd30e646 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 4
-SUBLEVEL = 239
+SUBLEVEL = 240
EXTRAVERSION =
NAME = Blurry Fish Butt
diff --git a/drivers/crypto/qat/qat_common/qat_algs.c
b/drivers/crypto/qat/
I'm announcing the release of the 5.8.16 kernel.
All users of the 5.8 kernel series must upgrade.
The updated 5.8.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.8.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index f342e64c8c1d..8db75cc76ed1 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 5
PATCHLEVEL = 4
-SUBLEVEL = 71
+SUBLEVEL = 72
EXTRAVERSION =
NAME = Kleptomaniac Octopus
diff --git a/arch/arm/boot/compressed/
I'm announcing the release of the 4.19.152 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web browser
I'm announcing the release of the 5.9.1 kernel.
All users of the 5.9 kernel series must upgrade.
The updated 5.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.9.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 6c787cd1cb51..a4622ef65436 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 5
PATCHLEVEL = 8
-SUBLEVEL = 15
+SUBLEVEL = 16
EXTRAVERSION =
NAME = Kleptomaniac Octopus
diff --git a/drivers/crypto/bcm/cipher
diff --git a/Makefile b/Makefile
index f2c9db9b4015..aa79ce7bfdc7 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 19
-SUBLEVEL = 151
+SUBLEVEL = 152
EXTRAVERSION =
NAME = "People's Front"
diff --git a/arch/arm/boot/compressed/M
I'm announcing the release of the 5.4.72 kernel.
All users of the 5.4 kernel series must upgrade.
The updated 5.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-5.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index e3e2d7fa7232..0284c231bdea 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 14
-SUBLEVEL = 201
+SUBLEVEL = 202
EXTRAVERSION =
NAME = Petit Gorille
diff --git a/drivers/crypto/bcm/cipher.c b
The function changed at some point, but the description was not
updated.
Signed-off-by: Qiujun Huang
---
kernel/trace/ring_buffer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
index b2c6f2546d69..598c388d6436 100644
Hi!
> > I'm getting this during boot: 32-bit thinkpad x60.
>
> This is very odd.
>
> The change in next is essentially a revert of a change, maybe I'm
> missing something and the revert isn't quite a revert. Although
> there was one difference.
>
> I'll check for other revert differences too.
>
Linus Torvalds writes:
> On Thu, Oct 15, 2020 at 8:24 PM Michael Ellerman wrote:
>>
>> Just two minor conflicts I'm aware of. The only slight subtlety is the
>> conflict
>> in kasan_init() where "int ret" needs to move out of the for_each_mem_range()
>> and up to the function scope.
>
> Well, th
On Wed, 2020-10-14 at 14:57 +0200, Joerg Roedel wrote:
> On Wed, Oct 14, 2020 at 03:25:08PM +0800, Lu Baolu wrote:
> > I suppose Joerg will pick this up. I guess you don't need to resend it
> > unless Joerg asks you to do.
>
> Yes, will pick this up soon, no need to re-send.
Please could it, and
Hi!
> +static int idt82p33_adjwritephase(struct ptp_clock_info *ptp, s32
> +offsetNs) {
adj_write_phase?
> + struct idt82p33_channel *channel =
> + container_of(ptp, struct idt82p33_channel, caps);
> + struct idt82p33 *idt82p33 = channel->idt82p33;
> + s64 offsetInFs;
>
On Wed, Oct 14, 2020 at 10:24 AM Pujin Shi wrote:
>
> This patch addresses a compile warning:
> fs/btrfs/extent-tree.c: In function '__btrfs_free_extent':
> fs/btrfs/extent-tree.c:3187:4: warning: format '%lu' expects argument of type
> 'long unsigned int', but argument 8 has type 'unsigned int'
Hi Guido.
On Sat, Oct 17, 2020 at 11:13:07AM +0200, Guido Günther wrote:
> Hi Sam,
> On Fri, Oct 16, 2020 at 04:29:16PM +0200, Sam Ravnborg wrote:
> > Hi Guido.
> > On Tue, Oct 13, 2020 at 12:32:45PM +0200, Guido Günther wrote:
> [..snip..]
> > >
> > > Changes from v1:
> > > - As per review comm
On Sat, Oct 17, 2020 at 5:49 AM Kees Cook wrote:
>
> On Fri, Oct 16, 2020 at 01:12:24AM -0700, syzbot wrote:
> > dashboard link: https://syzkaller.appspot.com/bug?extid=92ead4eb8e26a26d465e
> > [...]
> > Reported-by: syzbot+92ead4eb8e26a26d4...@syzkaller.appspotmail.com
> > [...]
> > UBSAN: array-
On Sat, Oct 17, 2020 at 12:50 PM Dmitry Vyukov wrote:
> On Sat, Oct 17, 2020 at 5:49 AM Kees Cook wrote:
> > On Fri, Oct 16, 2020 at 01:12:24AM -0700, syzbot wrote:
> > > dashboard link:
> > > https://syzkaller.appspot.com/bug?extid=92ead4eb8e26a26d465e
> > > [...]
> > > Reported-by: syzbot+92ea
Hi,
On Sat, Oct 17, 2020 at 11:49:43AM +0200, Greg Kroah-Hartman wrote:
> On Sat, Oct 17, 2020 at 11:41:53AM +0200, Salvatore Bonaccorso wrote:
> > hi,
> >
> > On Fri, Oct 16, 2020 at 12:01:51PM -0700, Guenter Roeck wrote:
> > > On Fri, Oct 16, 2020 at 11:07:19AM +0200, Greg Kroah-Hartman wrote:
Hi,
I looked into the warning "WARNING in md_ioctl" found by Syzkaller.
(https://syzkaller.appspot.com/bug?id=fbf9eaea2e65bfcabb4e2750c3ab0892867edea1)
I suspect that it is caused by a race between two concurrenct ioctl()s as
belows.
CPU1 (md_ioctl()) CPU2 (md_ioctl())
-
Hi Jean
On Fri, Oct 16, 2020 at 09:59:23AM +0200, Jean-Philippe Brucker wrote:
> On Thu, Oct 15, 2020 at 11:22:11AM -0700, Raj, Ashok wrote:
> > Hi Jean
> >
> > + Baolu who is looking into this.
> >
> >
> > On Thu, Oct 15, 2020 at 11:00:27AM +0200, Jean-Philippe Brucker wrote:
> > > Add a param
Hi,
in kernel 5.9, my Banana Pi test systems suffers from catastrophic
packet loss on the Ethernet that makes the machine nearly unusable.
Reverting bbc4d71d63549bcd003a430de18a72a742d8c91e fixes the issue for
me.
Please investigate the breakage caused by this commit. I am prepared to
help with t
On Fri, Oct 16, 2020 at 12:33:54PM +0200, Pavel Machek wrote:
> Hi!
>
> > This is the start of the stable review cycle for the 4.19.152 release.
> > There are 21 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> >
On Fri, Oct 16, 2020 at 05:45:56PM +0100, Jon Hunter wrote:
>
> On 16/10/2020 10:08, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.9.1 release.
> > There are 15 patches in this series, all will be posted as a response
> > to this one. If anyone has any issue
On Sat, Oct 17, 2020 at 12:33:06AM +0530, Naresh Kamboju wrote:
> On Fri, 16 Oct 2020 at 14:42, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 5.9.1 release.
> > There are 15 patches in this series, all will be posted as a response
> > to this one. If any
On Fri, Oct 16, 2020 at 02:09:42PM -0700, Guenter Roeck wrote:
> On Fri, Oct 16, 2020 at 11:08:02AM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.9.1 release.
> > There are 15 patches in this series, all will be posted as a response
> > to this one. If
Some old GCC versions between 4.5.0 and 4.9.1 might miscompile code
with -fvar-tracking-assingments (which is enabled by default with -g -O2).
commit 2062afb4f added -fno-var-tracking-assignments unconditionally to
work around this. But newer versions of GCC no longer have this bug, so
only add it
Hi,
Am Freitag, 2. Oktober 2020, 18:11:28 CEST schrieb Krzysztof Kozlowski:
> On Thu, Sep 17, 2020 at 08:52:10PM +0200, Krzysztof Kozlowski wrote:
> > GPIO_ACTIVE_x flags are not correct in the context of interrupt flags.
> > These are simple defines so they could be used in DTS but they will not
This patch addresses a compile warning:
fs/btrfs/extent-tree.c: In function '__btrfs_free_extent':
fs/btrfs/extent-tree.c:3187:4: warning: format '%lu' expects argument of type
'long unsigned int', but argument 8 has type 'unsigned int' [-Wformat=]
Fixes: 1c2a07f598d5 ("btrfs: extent-tree: kill B
Hi Yang.
Can you please resend and include Greg in the recipient list.
Greg is maintainer of the console subsystem these days.
Sam
On Mon, Jul 13, 2020 at 11:04:45AM +, Yang Yingliang wrote:
> I got a UAF report in do_update_region() when I doing fuzz test.
>
> [ 51.161905] BUG: K
Hi
> [...]
> >> +static int get_gpio_pin_state(struct irq_desc *irq_desc)
> >> +{
> >> + struct gpio_chip *gc = irq_data_get_irq_chip_data(&irq_desc->irq_data);
> >> +
> >> + return gc->get(gc, irq_desc->irq_data.hwirq);
> >> +}
> >> +
> >> +static bool interrupt_line_active(struct i2c_client *c
loop-AES changes since previous release:
- Worked around kernel interface changes on 5.9 kernels
- Partial re-write of ioctl handling to get rid of set_fs() which is
expected to be removed from mainline kernels in near future.
bzip2 compressed tarball is here:
http://loop-aes.sourceforge.n
Hello!
Il giorno ven 16 ott 2020 alle ore 10:46 Georgi Djakov
ha scritto:
>
> Hi,
>
> Thanks for the patch!
My pleasure!
>
> On 10/8/20 23:45, khol...@gmail.com wrote:
> > From: AngeloGioacchino Del Regno
> >
> > Introduce a driver for the Qualcomm interconnect busses found in
> > the SDM630/SD
After discussing this offline with Jann a bit, I have a few general
comments on the design of this.
First, the UUID communicated by the hypervisor should be consumed by
the kernel -- added as another input to the rng -- and then userspace
should be notified that it should reseed any userspace RNGs
On Fri, Oct 16, 2020 at 11:19:41PM -0400, j...@joelfernandes.org wrote:
> On Fri, Oct 16, 2020 at 09:27:53PM -0400, j...@joelfernandes.org wrote:
> [..]
> > > > + *
> > > > + * Memory barrier is needed after adding to length for the case
> > > > + * where length transitions from 0 -> 1. This is bec
From: AngeloGioacchino Del Regno
Add the bindings for the Qualcomm SDM660-class NoC, valid for
SDM630, SDM636, SDM660 and SDA variants.
Signed-off-by: AngeloGioacchino Del Regno
---
.../bindings/interconnect/qcom,sdm660.yaml| 147 ++
.../dt-bindings/interconnect/qcom,sdm660
From: AngeloGioacchino Del Regno
Introduce a driver for the Qualcomm interconnect busses found in
the SDM630/SDM636/SDM660 SoCs.
The topology consists of several NoCs that are controlled by a
remote processor that collects the aggregated bandwidth for each
master-slave pairs.
On a note, these ch
From: AngeloGioacchino Del Regno
This patch series adds the SDM660 interconnect provider driver in
order to stop some timeouts and achieve some decent performance by
avoiding to be NoC limited.
It's also providing some power consumption improvement, but I have
only measured that as less heat, whi
On Thu, Oct 15, 2020 at 12:34:06AM +0300, Jarkko Sakkinen wrote:
> Konstantin, writing to you based on 'git blame' :-)
>
> The maintainer guide recommends using paperkey for the PGP master key,
> which is a prefectly sane method.
>
> I was just wondering that isn't a backup to a USB stick a reaso
--
Good day and God bless you as you read this massage, I am Aadila
Laboso a 27 years old girl from Kenya, my mother was Late Mrs. Lorna
Laboso the former Kenyan Assistant Minister of Home and affairs who
was among plan that crash board in the remote area of Kalong’s western
Kenya Read more about
Hi,
On Sat, Oct 17, 2020 at 01:06:14PM +, Barnabás Pőcze wrote:
Hi
[...]
>> +static int get_gpio_pin_state(struct irq_desc *irq_desc)
>> +{
>> + struct gpio_chip *gc =
irq_data_get_irq_chip_data(&irq_desc->irq_data);
>> +
>> + return gc->get(gc, irq_desc->irq_data.hwirq);
>> +}
Hi Mauro,
I'm reposting this series [1] as, following the merge window, it now
cleanly applies to both Linus' tree and to linux-next. I've made a minor
fix to patch #1 (see patch for details) but the other two patches have
just been rebased.
Best,
Alex
[1] See
https://lore.kernel.org/lkml/20200
We don't really need to know that the LED pin reset successfully.
Signed-off-by: Alex Dewar
---
drivers/staging/media/atomisp/i2c/atomisp-lm3554.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/media/atomisp/i2c/atomisp-lm3554.c
b/drivers/staging/media/atomisp/i2c/atomisp-lm
The function lm3554_remove() checks for the return code for
lm3554_gpio_uninit() even though this is on the exit path and exits the
function, leaving the variable flash unfreed. Instead, print a warning and
free flash unconditionally.
Signed-off-by: Alex Dewar
---
.../staging/media/atomisp/i2c/a
On 10/16/20 7:52 PM, Tian Tao wrote:
> Remove including that don't need it.
Applied, thanks.
--
Jens Axboe
The error path for lm3554_probe() contains a number of bugs, including:
* resource leaks
* jumping to error labels out of sequence
* not setting the return value appropriately
Fix it up and give the labels more memorable names.
This issue has existed since the code was originally contributed i
From: Tom Rix
Remove the trailing error message from the fixed lines
Signed-off-by: Tom Rix
---
v2: fix whitespace
---
scripts/checkpatch.pl | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index fab38b493cef..f9e78a5385ad
On Sat, 2020-10-17 at 07:25 -0700, t...@redhat.com wrote:
> From: Tom Rix
>
> Remove the trailing error message from the fixed lines
>
> Signed-off-by: Tom Rix
> ---
> v2: fix whitespace
Thanks Tom. Andrew can you pick this up please?
> ---
> scripts/checkpatch.pl | 7 +--
> 1 file chan
The function ia_css_mipi_frame_specify() is not called from anywhere and
the comment above its declaration states that it should be removed when
there are no more users. So remove it.
Signed-off-by: Alex Dewar
---
drivers/staging/media/atomisp/pci/ia_css_mipi.h | 17 -
drivers/st
The bodies of the if and else sections are the same, so just remove the
check.
Signed-off-by: Alex Dewar
---
.../staging/media/atomisp/pci/atomisp_cmd.c | 27 +--
1 file changed, 6 insertions(+), 21 deletions(-)
diff --git a/drivers/staging/media/atomisp/pci/atomisp_cmd.c
b/d
On Fri, Oct 16, 2020 at 09:27:53PM -0400, j...@joelfernandes.org wrote:
> Adding Alan as well as its memory barrier discussion ;-)
I don't know the internals of how RCU works, so I'll just speak to the
litmus test itself, ignoring issues of whether the litmus test is
appropriate or expresses wha
On Sat, Oct 17, 2020 at 1:02 PM Jann Horn wrote:
> > > > dashboard link:
> > > > https://syzkaller.appspot.com/bug?extid=92ead4eb8e26a26d465e
> > > > [...]
> > > > Reported-by: syzbot+92ead4eb8e26a26d4...@syzkaller.appspotmail.com
> > > > [...]
> > > > UBSAN: array-index-out-of-bounds in crypto/a
> [...]
> >> >> +static int get_gpio_pin_state(struct irq_desc *irq_desc)
> >> >> +{
> >> >> + struct gpio_chip *gc =
> >> >> irq_data_get_irq_chip_data(&irq_desc->irq_data);
> >> >> +
> >> >> + return gc->get(gc, irq_desc->irq_data.hwirq);
> >> >> +}
> >> >> +
> >> >> +static bool int
1 - 100 of 233 matches
Mail list logo
