On Sun, 31 Jan 2021 11:09:14 +0100,
Dinghao Liu wrote:
>
> When device_type == DEVICE_ALI, we should also check the return
> value of pci_iomap() to avoid potential null pointer dereference.
>
> Signed-off-by: Dinghao Liu
Thanks, applied.
Takashi
When one page is already hwpoisoned by AO action, process may not be
killed, the process mapping this page may make a syscall include this
page and result to trigger a VM_FAULT_HWPOISON fault, if it's in kernel
mode it may be fixed by fixup_exception. Current code will just return
error code to
Open /dev/nbdX first, the config_refs will be 1 and
the pointers in nbd_device are still null. Disconnect
/dev/nbdX, then reference a null recv_workq. The
protection by config_refs in nbd_genl_disconnect is useless.
[ 656.366194] BUG: kernel NULL pointer dereference, address: 0020
[
>
> On Mon, Feb 01, 2021 at 07:51:19AM +, Avri Altman wrote:
> > >
> > > On Mon, Feb 01, 2021 at 07:12:53AM +, Avri Altman wrote:
> > > > > > +#define WORK_PENDING 0
> > > > > > +#define ACTIVATION_THRSHLD 4 /* 4 IOs */
> > > > > Rather than fixing it with macro, how about using sysfs and
On 01/02/2021 06:45, Bilal Wasim wrote:
> When "bus_prot_reg_update" is false, the driver should use
> INFRA_TOPAXI_PROTECTEN for both setting and clearing the bus
> protection. However, the driver does not use this mask for
> clearing bus protection which causes failure when booting
> the
> From: Alex Williamson
> Sent: Saturday, January 30, 2021 6:58 AM
>
> On Mon, 25 Jan 2021 17:03:58 +0800
> Shenming Lu wrote:
>
> > Hi,
> >
> > The static pinning and mapping problem in VFIO and possible solutions
> > have been discussed a lot [1, 2]. One of the solutions is to add I/O
> >
Kasan function that populates the shadow regions used to allocate them
page by page and did not take advantage of hugepages, so fix this by
trying to allocate hugepages of 1GB and fallback to 2MB hugepages or 4K
pages in case it fails.
This reduces the page table memory consumption and improves
On Sun, Jan 31, 2021 at 1:43 AM Kent Gibson wrote:
>
> On Sat, Jan 30, 2021 at 09:37:55PM +0100, Bartosz Golaszewski wrote:
> > On Fri, Jan 29, 2021 at 4:57 PM Andy Shevchenko
> > wrote:
> > >
> > > On Fri, Jan 29, 2021 at 02:46:24PM +0100, Bartosz Golaszewski wrote:
> > > > From: Bartosz
Hi Sakari,
On Thu, Jan 14, 2021 at 06:04:24PM +0100, Jacopo Mondi wrote:
> One more iteration to squash in all the fixups sent in v7 and address
> a comment from Sergei in [2/5] commit message.
>
> All patches now reviewed and hopefully ready to be collected!
All patches seems reviewed, do you
On 01.02.2021 11:26, Stefano Garzarella wrote:
> On Sun, Jan 31, 2021 at 01:59:14PM +0300, Alexander Popov wrote:
>> There are multiple similar bugs implicitly introduced by the
>> commit c0cfa2d8a788fcf4 ("vsock: add multi-transports support") and
>> commit 6a2c0962105ae8ce ("vsock: prevent
On Fri, Jan 29, 2021 at 1:20 PM Sakari Ailus
wrote:
>
> Hi Bartosz,
>
> Thanks for the review.
>
> On Fri, Jan 29, 2021 at 11:56:00AM +0100, Bartosz Golaszewski wrote:
> > On Fri, Jan 29, 2021 at 12:27 AM Sakari Ailus
> > wrote:
> > >
> > > In certain use cases (where the chip is part of a
Hi Greg,
On 29/01/2021 15:14, Josh Poimboeuf wrote:
> On Fri, Jan 29, 2021 at 12:09:53PM +0100, Greg Kroah-Hartman wrote:
>> On Fri, Jan 29, 2021 at 11:03:26AM +, Chris Clayton wrote:
>>>
>>>
>>> On 29/01/2021 10:11, Greg Kroah-Hartman wrote:
On Thu, Jan 28, 2021 at 10:00:15AM -0600,
On 01/02/21 09:38, Jiapeng Chong wrote:
Fix the following coccicheck warning:
./arch/x86/kvm/debugfs.c:44:0-23: WARNING: vcpu_tsc_scaling_frac_fops
should be defined with DEFINE_DEBUGFS_ATTRIBUTE.
./arch/x86/kvm/debugfs.c:36:0-23: WARNING: vcpu_tsc_scaling_fops should
be defined with
On Mon, Feb 1, 2021 at 12:05 AM Marek Szyprowski
wrote:
>
> Hi Saravana,
>
> On 30.01.2021 05:08, Saravana Kannan wrote:
> > On Fri, Jan 29, 2021 at 8:03 PM Saravana Kannan
> > wrote:
> >> This patch series solves two general issues with fw_devlink=on
> >>
> >> Patch 1/2 addresses the issue of
On 2021-01-30 00:55, Bean Huo wrote:
On Tue, 2021-01-19 at 17:37 +0530, Nitin Rawat wrote:
As per JESD223D UFS HCI v3.0 spec, HCI version 3.0
is also supported. Hence Adding UFS3.0 in UFS HCI
version check to avoid logging of the error message.
Signed-off-by: Nitin Rawat
---
Hello,
syzbot found the following issue on:
HEAD commit:6642d600 Merge tag '5.11-rc5-smb3' of git://git.samba.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16f064acd0
kernel config: https://syzkaller.appspot.com/x/.config?x=9408d1770a50819c
On 11.01.21 20:40, Mike Rapoport wrote:
From: Mike Rapoport
There could be struct pages that are not backed by actual physical memory.
This can happen when the actual memory bank is not a multiple of
SECTION_SIZE or when an architecture does not register memory holes
reserved by the firmware
Hello,
syzbot found the following issue on:
HEAD commit:14e8e0f6 tcp: shrink inet_connection_sock icsk_mtup enable..
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=114362c4d0
kernel config: https://syzkaller.appspot.com/x/.config?x=ac6e76902c1abb76
Hello,
syzbot found the following issue on:
HEAD commit:b01f250d Add linux-next specific files for 20210129
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=160cda90d0
kernel config: https://syzkaller.appspot.com/x/.config?x=725bc96dc234fda7
dashboard
commit 5d399d05df42ffcaa2b3836b580631c4024487a0
Author: Kurt Garloff
Date: Mon Feb 1 09:01:47 2021 +
turbostat: Fix Pkg Power tracking on Zen
AMD Zen processors use a different MSR (MSR_PKG_ENERGY_STAT) than intel
(MSR_PKG_ENERGY_STATUS) to track package power; however we
Hello,
syzbot found the following issue on:
HEAD commit:b01f250d Add linux-next specific files for 20210129
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14daa408d0
kernel config: https://syzkaller.appspot.com/x/.config?x=725bc96dc234fda7
dashboard
Hello,
syzbot found the following issue on:
HEAD commit:6642d600 Merge tag '5.11-rc5-smb3' of git://git.samba.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=148aef78d0
kernel config: https://syzkaller.appspot.com/x/.config?x=9408d1770a50819c
Fix the following coccicheck warning:
./drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c:1591:0-23: WARNING:
fops_sclk_set should be defined with DEFINE_DEBUGFS_ATTRIBUTE.
./drivers/gpu/drm/amd/amdgpu/amdgpu_debugfs.c:1588:0-23: WARNING:
fops_ib_preempt should be defined with
During cpufreq driver's registration, if the ->init() callback for all
the CPUs fail then there is not much point in keeping the driver around
as it will only account for more unnecessary noise, for example cpufreq
core will try to suspend/resume the driver which never got registered
properly.
Eliminate the following coccicheck warning:
./sound/soc/fsl/fsl_xcvr.c:739:2-3: Unneeded semicolon
Reported-by: Abaci Robot
Signed-off-by: Yang Li
---
sound/soc/fsl/fsl_xcvr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/fsl/fsl_xcvr.c
On Sun, Jan 31, 2021 at 01:59:14PM +0300, Alexander Popov wrote:
There are multiple similar bugs implicitly introduced by the
commit c0cfa2d8a788fcf4 ("vsock: add multi-transports support") and
commit 6a2c0962105ae8ce ("vsock: prevent transport modules unloading").
The bug pattern:
[1]
Hi,
On 2/1/21 3:36 AM, Perry Yuan wrote:
> Hi Hans.
> Could you share your the commit link after you apply this patch to your
> for-next branch?
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=for-next=64b0efa18f8c3b1baac369b8d74d0fdae02bc4bc
On Sat, 30 Jan 2021, Joe Perches wrote:
> On Mon, 2020-08-24 at 21:56 -0700, Joe Perches wrote:
>> Use semicolons and braces.
>
> Ping?
Seems to have fallen between the cracks.
The first two hunks have been fixed, the last two are still there. Care
to respin and rebase against drm-tip (or
Quoting Jani Nikula (2021-01-28 13:23:48)
>
> A number of our CI systems are hitting redzone overwritten errors after
> s2idle, with the errors introduced between v5.11-rc4 and v5.11-rc5. See
> snippet below, full logs for one affected machine at [1].
>
> Known issue?
Fwiw, I think this should
On Mon, Feb 1, 2021 at 4:35 AM Zhen Lei wrote:
>
> Enable support for the Hisilicon Kunpeng506 and Kunpeng509 SoC.
>
> Signed-off-by: Zhen Lei
Reviewed-by: Arnd Bergmann
Russell, do you have a preference for how to get this series merged
after the last comments are resolved?
I think there is
From: Wanpeng Li
The per-cpu vsyscall pvclock data pointer assigns either an element of the
static array hv_clock_boot (#vCPU <= 64) or dynamically allocated memory
hvclock_mem (vCPU > 64), the dynamically memory will not be allocated if
kvmclock vsyscall is disabled, this can result in cpu
Eliminate the following coccicheck warning:
./scripts/gcc-plugins/latent_entropy_plugin.c:527:2-3: Unneeded
semicolon
Reported-by: Abaci Robot
Signed-off-by: Yang Li
---
scripts/gcc-plugins/latent_entropy_plugin.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Sat, Jan 30, 2021 at 10:20 PM Uwe Kleine-König
wrote:
>
> Hello,
>
> On Fri, Jan 29, 2021 at 02:46:16PM +0100, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski
> >
> > This series adds a new GPIO testing module based on configfs committable
> > items
> > and sysfs. The goal is to
On 29/01/21 17:58, Sean Christopherson wrote:
On Fri, Jan 29, 2021, Paolo Bonzini wrote:
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 76bce832cade..15733013b266 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -1401,7 +1401,7 @@ static u64
There are multiple similar bugs implicitly introduced by the
commit c0cfa2d8a788fcf4 ("vsock: add multi-transports support") and
commit 6a2c0962105ae8ce ("vsock: prevent transport modules unloading").
The bug pattern:
[1] vsock_sock.transport pointer is copied to a local variable,
[2]
On 2/1/21 9:47 AM, Chao Leng wrote:
On 2021/2/1 15:29, Hannes Reinecke wrote:[ .. ]
Urgh. Please, no. That is well impossible to debug.
Can you please open-code it to demonstrate where the difference to the
current (and my fixed) versions is?
I'm still not clear where the problem is once we
Hi Len,
Issue persists on Ryzen in 5.11-rc6:
kvmadmin@KurtSrv2018(//):~ [0]$ sudo
/casa/src/linux-stable/tools/power/x86/turbostat/turbostat
turbostat version 20.09.30 - Len Brown
CPUID(0): AuthenticAMD 0x10 CPUID levels; 0x8023 xlevels;
family:model:stepping 0x19:21:0 (25:33:0)
CPUID(1):
> On Mon, Feb 01, 2021 at 08:17:59AM +, Avri Altman wrote:
> > >
> > > On Mon, Feb 01, 2021 at 07:51:19AM +, Avri Altman wrote:
> > > > >
> > > > > On Mon, Feb 01, 2021 at 07:12:53AM +, Avri Altman wrote:
> > > > > > > > +#define WORK_PENDING 0
> > > > > > > > +#define
On Sun, Jan 31, 2021 at 09:24:32AM -0800, Andy Lutomirski wrote:
> While we're at it, disable the workaround on all CPUs except AMD Family
> 0xF. By my reading of the Revision Guide for AMD Athlon™ 64 and AMD
> Opteron™ Processors, only family 0xF is affected.
I think it would be better to have
Hello,
syzbot found the following issue on:
HEAD commit:6642d600 Merge tag '5.11-rc5-smb3' of git://git.samba.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13f36b44d0
kernel config: https://syzkaller.appspot.com/x/.config?x=96b123631a6700e9
Hello,
syzbot found the following issue on:
HEAD commit:6642d600 Merge tag '5.11-rc5-smb3' of git://git.samba.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=171405bf50
kernel config: https://syzkaller.appspot.com/x/.config?x=9408d1770a50819c
On Sun, 2021-01-31 at 21:26 -0800, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:bec4c296 Merge tag 'ecryptfs-5.11-rc6-setxattr-fix' of git..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=11991778d0
> kernel
On Sun, Jan 31, 2021 at 09:24:40AM -0800, Andy Lutomirski wrote:
> + kernelmode_fixup_or_oops(regs, error_code, address, pkey,
> si_code);
> if (!user_mode(regs)) {
> - no_context(regs, error_code, address, SIGBUS, BUS_ADRERR);
> +
On 01/02/2021 06:45, Bilal Wasim wrote:
> The mfg_async power domain in mt8173 is used to power up imgtec
> gpu. This domain requires the da9211 regulator to be enabled before
> the power domain can be enabled successfully.
>
> Signed-off-by: Bilal Wasim
> ---
>
Hi all,
Changes since 20210129:
Removed tree: ia64 (deprecated with maintainer's permission)
The drm tree gained a conflict against Linus' tree.
The drm-misc tree gained a build failure so I used the version from
next-20210129.
The tip tree gained a boot failure so I reverted a commit.
The
Hello,
syzbot found the following issue on:
HEAD commit:78031381 bpf: Drop disabled LSM hooks from the sleepable set
git tree: bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=11274530d0
kernel config: https://syzkaller.appspot.com/x/.config?x=be33d8015c9de024
On Fri, Jan 29, 2021 at 6:36 PM syzbot
wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 8d1ddb5e79374fb277985a6b3faa2ed8631c5b4c
> Author: Boqun Feng
> Date: Thu Nov 5 06:23:51 2020 +
>
> fcntl: Fix potential deadlock in send_sig{io, urg}()
>
> bisection log:
Hi Saravana,
On 30.01.2021 05:08, Saravana Kannan wrote:
> On Fri, Jan 29, 2021 at 8:03 PM Saravana Kannan wrote:
>> This patch series solves two general issues with fw_devlink=on
>>
>> Patch 1/2 addresses the issue of firmware nodes that look like they'll
>> have struct devices created for
On Sun, 31 Jan 2021 15:53:20 +0100,
Sean Young wrote:
>
> On Wed, Jan 20, 2021 at 11:20:56AM +0100, Takashi Iwai wrote:
> > dvb_usb_device_init() allocates a dvb_usb_device object, but it
> > doesn't release it even when returning an error. The callers don't
> > seem caring it as well, hence
Fix the following coccicheck warning:
./drivers/crypto/caam/debugfs.c:23:0-23: WARNING: caam_fops_u64_ro
should be defined with DEFINE_DEBUGFS_ATTRIBUTE.
./drivers/crypto/caam/debugfs.c:22:0-23: WARNING: caam_fops_u32_ro
should be defined with DEFINE_DEBUGFS_ATTRIBUTE.
Reported-by: Abaci Robot
On 2021-01-31 04:16, Xie He wrote:
On Sat, Jan 30, 2021 at 11:16 AM Jakub Kicinski
wrote:
Sounds like too much afford for a sub-optimal workaround.
The qdisc semantics are borken in the proposed scheme (double
counting packets) - both in term of statistics and if user decides
to add a
HI Chunfeng,
On Mon, Feb 1, 2021 at 1:58 PM Chunfeng Yun wrote:
>
> For those unchecked endpoints, we don't allocate bandwidth for
> them, so no need free the bandwidth, otherwise will decrease
> the allocated bandwidth.
> Meanwhile use xhci_dbg() instead of dev_dbg() to print logs and
> rename
On Mon, Feb 01, 2021 at 07:51:19AM +, Avri Altman wrote:
> >
> > On Mon, Feb 01, 2021 at 07:12:53AM +, Avri Altman wrote:
> > > > > +#define WORK_PENDING 0
> > > > > +#define ACTIVATION_THRSHLD 4 /* 4 IOs */
> > > > Rather than fixing it with macro, how about using sysfs and make it
> > >
Eliminate the following coccicheck warning:
./sound/soc/intel/catpt/pcm.c:355:2-3: Unneeded semicolon
Reported-by: Abaci Robot
Signed-off-by: Yang Li
---
sound/soc/intel/catpt/pcm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/intel/catpt/pcm.c
From: "Maciej S. Szmigiero"
When retpolines are enabled they have high overhead in the inner loop
inside kvm_handle_hva_range() that iterates over the provided memory area.
Implement a static dispatch there, just like commit 7a02674d154d
("KVM: x86/mmu: Avoid retpoline on ->page_fault() with
This patch removes unneeded return variables, using only
'0' instead.
It fixes the following warning detected by coccinelle:
./scripts/gcc-plugins/structleak_plugin.c:173:14-17: Unneeded variable:
"ret". Return "0" on line 203
Reported-by: Abaci Robot
Signed-off-by: Yang Li
---
From: "Maciej S. Szmigiero"
The current memslot code uses a (reverse) gfn-ordered memslot array for
keeping track of them.
This only allows quick binary search by gfn, quick lookup by hva is not
possible (the implementation has to do a linear scan of the whole memslot
array).
Because the
On Mon, Feb 1, 2021 at 4:36 AM Zhen Lei wrote:
>
> Add support for the Hisilicon Kunpeng L3 cache controller as used with
> Kunpeng506 and Kunpeng509 SoCs.
>
> These Hisilicon SoCs support LPAE, so the physical addresses is wider than
> 32-bits, but the actual bit width does not exceed 36 bits.
dvb_usb_device_init() allocates a dvb_usb_device object, but it
doesn't release the object by itself even at errors. The object is
released in the callee side (dvb_usb_init()) in some error cases via
dvb_usb_exit() call, but it also missed the object free in other error
paths. And, the caller
dvb_usb_device_init() copies the properties to the own data, so that
the callers can release the original properties later (as done in the
commit 299c7007e936 "media: dw2102: Fix memleak on sequence of
probes"). However, it also stores dev->desc pointer that is a
reference to the original
On Sun, Jan 31, 2021 at 05:31:43PM +0200, Max Gurtovoy wrote:
On 1/28/2021 4:41 PM, Stefano Garzarella wrote:
From: Max Gurtovoy
This will allow running vDPA for virtio block protocol.
Signed-off-by: Max Gurtovoy
[sgarzare: various cleanups/fixes]
Signed-off-by: Stefano Garzarella
---
v2:
Hi,
here is a revised patch set to address the use-after-free at
disconnecting a USB DVB device that was recently reported on openSUSE
Bugzilla. The bug itself seems to be a long-standing one, and I
spotted another memory leak there, which is covered in the first
patch.
This revision addressed
On 2021-01-31 19:32, Avri Altman wrote:
UFS specification allows different VCC configurations for UFS devices,
for example,
(1)2.70V - 3.60V (For UFS 2.x devices)
(2)2.40V - 2.70V (For UFS 3.x devices)
For platforms supporting both ufs 2.x (2.7v-3.6v) and
ufs 3.x (2.4v-2.7v),
On 2021/1/29 10:52, Liuxiangdong (Aven, Cloud Infrastructure Service
Product Dept.) wrote:
On 2021/1/26 15:08, Xu, Like wrote:
On 2021/1/25 22:47, Liuxiangdong (Aven, Cloud Infrastructure Service
Product Dept.) wrote:
Thanks for replying,
On 2021/1/25 10:41, Like Xu wrote:
+
On Mon, Feb 01, 2021 at 08:17:59AM +, Avri Altman wrote:
> >
> > On Mon, Feb 01, 2021 at 07:51:19AM +, Avri Altman wrote:
> > > >
> > > > On Mon, Feb 01, 2021 at 07:12:53AM +, Avri Altman wrote:
> > > > > > > +#define WORK_PENDING 0
> > > > > > > +#define ACTIVATION_THRSHLD 4 /* 4 IOs
From: "Maciej S. Szmigiero"
The KVM selftest framework was using a simple list for keeping track of
the memslots currently in use.
This resulted in lookups and adding a single memslot being O(n), the
later due to linear scanning of the existing memslot set to check for
the presence of any
On 2021-01-31 19:29, Avri Altman wrote:
Exporting functions ufshcd_set_dev_pwr_mode, ufshcd_disable_vreg
and ufshcd_enable_vreg so that vendor drivers can make use of
them in setting vendor specific regulator setting
in vendor specific file.
As for ufshcd_{enable,disable}_vreg - maybe inline
From: "Maciej S. Szmigiero"
This benchmark contains the following tests:
* Map test, where the host unmaps guest memory while the guest writes to
it (maps it).
The test is designed in a way to make the unmap operation on the host
take a negligible amount of time in comparison with the mapping
On Tue, Aug 25, 2020 at 6:57 AM Joe Perches wrote:
>
> Use semicolons and braces.
Reference to coding style doc? Or other important reason? Or just
personal preference?
Thanks,
Miklos
On 01/02/21 09:13, Maciej S. Szmigiero wrote:
static int kvm_handle_hva_range(struct kvm *kvm,
unsigned long start,
unsigned long end,
@@ -1495,8 +1534,9 @@ static int kvm_handle_hva_range(struct kvm *kvm,
-static int
On Sun, 31 Jan 2021 16:04:56 +0100,
Sean Young wrote:
>
> Hi Takashi,
>
> On Fri, Jan 22, 2021 at 04:47:44PM +0100, Robert Foss wrote:
> > Hey Takashi,
> >
> > This patch is generating a checkpatch warning, but I think it is
> > spurious and can be ignored.
>
> The checkpatch warning isn't
Rework calculation code of the Hugepage size to make it more readable and
straightforward.
Signed-off-by: Miaohe Lin
---
fs/hugetlbfs/inode.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c
index 3a08fbae3b53..1be18de4b537
On 2021-01-29, Petr Mladek wrote:
>> diff --git a/include/linux/printk.h b/include/linux/printk.h
>> index fe7eb2351610..6d8f844bfdff 100644
>> --- a/include/linux/printk.h
>> +++ b/include/linux/printk.h
>> @@ -45,6 +45,7 @@ static inline const char *printk_skip_headers(const char
>> *buffer)
Fix the following coccicheck warning:
./arch/x86/kvm/debugfs.c:44:0-23: WARNING: vcpu_tsc_scaling_frac_fops
should be defined with DEFINE_DEBUGFS_ATTRIBUTE.
./arch/x86/kvm/debugfs.c:36:0-23: WARNING: vcpu_tsc_scaling_fops should
be defined with DEFINE_DEBUGFS_ATTRIBUTE.
On 2021/2/1 15:29, Hannes Reinecke wrote:
On 2/1/21 3:16 AM, Chao Leng wrote:
On 2021/1/29 17:20, Hannes Reinecke wrote:
On 1/29/21 9:46 AM, Chao Leng wrote:
On 2021/1/29 16:33, Hannes Reinecke wrote:
On 1/29/21 8:45 AM, Chao Leng wrote:
On 2021/1/29 15:06, Hannes Reinecke wrote:
On Fri, Jan 29, 2021 at 09:37:30AM -0800, Sean Christopherson wrote:
> On Thu, Jan 28, 2021, ira.we...@intel.com wrote:
> > From: Ira Weiny
> >
> > There is no reason to alloc a page and kmap it to store this temporary
> > data from the user.
>
> Actually, there is, it's just poorly
On 31/01/2021 17:17, Chun-Kuang Hu wrote:
> Hi, Matthias:
>
> 於 2021年1月31日 週日 下午6:17寫道：
>>
>> From: Matthias Brugger
>>
>> The header file of GCE should be for MT8183 SoC instead of MT8173.
>>
>
> Reviewed-by: Chun-Kuang Hu
>
Applied to v5.11-next/dts64
Thanks
>> Fixes: 91f9c963ce79
On Sun, Jan 31, 2021 at 11:28 AM Dmitry Vyukov wrote:
>
> On Sun, Jan 31, 2021 at 11:04 AM Dmitry Vyukov wrote:
> >
> > On Thu, Nov 12, 2020 at 11:43 AM Dmitry Vyukov wrote:
> > > > > for sampling race detection),
> > > > > number of threads in the process can be up to, say, ~~10K and the
> > >
On 31/01/2021 23:23, Arnd Bergmann wrote:
> On Sun, Jan 31, 2021 at 3:07 PM Matthias Brugger
> wrote:
>> On 23/12/2020 09:44, Neal Liu wrote:
>>> Support DEVAPC on MediaTek platforms by enabling CONFIG_MTK_DEVAPC.
>>>
>>> Signed-off-by: Neal Liu
>>> ---
>>> arch/arm64/configs/defconfig |
Hello,
syzbot found the following issue on:
HEAD commit:73d62e81 kmsan: random: prevent boot-time reports in _mix_..
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=120020acd0
kernel config:
Hello,
syzbot found the following issue on:
HEAD commit:73d62e81 kmsan: random: prevent boot-time reports in _mix_..
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=12a62e6f50
kernel config:
On 31/01/2021 13:05, Matthias Brugger wrote:
>
>
> On 29/01/2021 11:12, Hsin-Yi Wang wrote:
>> Add domain supply node.
>>
>> Signed-off-by: Hsin-Yi Wang
>> ---
>
> Applied to v5.11-next/dts64
>
I just realiezed that we will also need a patch for the MT8183 EVB. I'll leave
this series in, but
On 01/02/21 09:46, Paolo Bonzini wrote:
This comment be updated to call out the new TSX_CTRL behavior.
/*
* On TAA affected systems:
* - nothing to do if TSX is disabled on the host.
* - we emulate TSX_CTRL if present on the host.
* This lets the guest
On Sun, Jan 31, 2021 at 09:24:37AM -0800, Andy Lutomirski wrote:
> #if defined(CONFIG_X86_64) && defined(CONFIG_CPU_SUP_AMD)
> + if (likely(boot_cpu_data.x86_vendor != X86_VENDOR_AMD
> +|| boot_cpu_data.x86 != 0xf))
Same nitpick as for the other patch. Maybe we wan a little
Hi all,
After merging the tip tree, today's linux-next qemu boot test (powerpc
pseries_le_defconfig) failed like this:
[0.005355][T1] smp: Brought up 1 node, 1 CPU
[0.005415][T1] numa: Node 0 CPUs: 0
[0.005496][T1] BUG: Unable to handle kernel instruction fetch (NULL
On 01.02.21 04:25, Anshuman Khandual wrote:
This overrides arch_get_mappabble_range() on s390 platform which will be
used with recently added generic framework. It modifies the existing range
check in vmem_add_mapping() using arch_get_mappable_range(). It also adds a
VM_BUG_ON() check that would
On 1/21/21 11:26 AM, Michal Simek wrote:
> Hi,
>
> I am sending this series to reflect the latest drivers which have been
> merged to mainline kernel. I have boot it on zcu102-rev1.0 and also
> zcu104-rev1.0. That's why I have also added DT for this newer revision.
>
> The series is based on
On Mon, Feb 01, 2021 at 08:59:09AM +, Chris Clayton wrote:
> Hi Greg,
>
> On 29/01/2021 15:14, Josh Poimboeuf wrote:
> > On Fri, Jan 29, 2021 at 12:09:53PM +0100, Greg Kroah-Hartman wrote:
> >> On Fri, Jan 29, 2021 at 11:03:26AM +, Chris Clayton wrote:
> >>>
> >>>
> >>> On 29/01/2021
On 1/21/21 11:27 AM, Michal Simek wrote:
> Xilinx ZynqMP zcu104 revC and newer board revisions have different i2c
> structure compare to revA. The rest of the board is the same from software
> perspective.
> Also enable DMAs and QSPI.
>
> Signed-off-by: Michal Simek
> ---
>
> Changes in v2:
On Mon, Feb 1, 2021 at 11:21 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:6642d600 Merge tag '5.11-rc5-smb3' of git://git.samba.org/..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=148aef78d0
> kernel config:
On 1/30/21 1:57 PM, Qiang Yu wrote:
This patch gets minor improvement on glmark2 (160->162).
It has bigger impact when the load is changing and the frequency
is stuck to min w/o this patch.
Seems there's no way for user to change this value, do we?
Or there's work pending to expose it to
From: Patrice Chotard
This series:
_ Update st.com to foss.st.com email for some maintainers.
_ Remove Vincent Abriou as STI/STM DRM driver
_ Add Alain Volmat as I2C/SMBUS driver maintainer
Patrice Chotard (3):
MAINTAINERS: Update some st.com email addresses to foss.st.com
From: Patrice Chotard
Remove Vincent Abriou's email as he has no more review activities on
STM/STI DRM drivers.
Signed-off-by: Patrice Chotard
Cc: Vincent Abriou
---
MAINTAINERS | 2 --
1 file changed, 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8222e50a9902..98365c57ae37
Hi,
On 1/31/21 3:30 PM, Nobuhiro Iwamatsu wrote:
> zynqmp_pm_get_eemi_ops() was removed in commit 4db8180ffe7c: "Firmware:
> xilinx:
> Remove eemi ops for fpga related APIs", but not in
> IS_REACHABLE(CONFIG_ZYNQMP_FIRMWARE).
> This removed zynqmp_pm_get_eemi_ops() in
>
On Wed, 27 Jan 2021 at 09:42, Abaci Team wrote:
>
> Fix the following coccicheck warnings:
>
> ./drivers/base/power/domain.c:938:31-33: WARNING !A || A && B is
> equivalent to !A || B.
>
> Reported-by: Abaci Robot
> Suggested-by: Jiapeng Zhong
> Signed-off-by: Abaci Team
Acked-by: Ulf Hansson
Hello,
syzbot found the following issue on:
HEAD commit:d03154e8 Add linux-next specific files for 20210128
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=16156808d0
kernel config: https://syzkaller.appspot.com/x/.config?x=6953ffb584722a1
dashboard
The ARM_SMMU_V3_PMU dependency on ARM_SMMU_V3_PMU was added with the idea
that a SMMUv3 PMCG would only exist on a system with an associated SMMUv3.
However it is not the job of Kconfig to make these sorts of decisions (even
if it were true), so remove the dependency.
Signed-off-by: John Garry
The Samsung Galaxy S5 uses the samsung s6e3fa2 AMOLED cmd LCD panel.
This driver was generated with [1], with the addition of
mipi_dsi_dcs_set_display_on at the end of the on method.
[1] https://github.com/msm8916-mainline/linux-mdss-dsi-panel-driver-generator
Signed-off-by: Iskren Chernev
---
Instead of relying purely on the special-case wrapper in bringup_cpu()
to pass the idle thread to __cpu_up(), expose idle_thread_get() so that
the architecture code can obtain it directly when necessary.
This will be useful when the existing __cpu_up() is split into multiple
phases, only *one* of
On 2/1/21 7:32 AM, Stefan Berger wrote:
Detect whether a key is an sm2 type of key by its OID in the parameters
array rather than assuming that everything under OID_id_ecPublicKey
is sm2, which is not the case.
Signed-off-by: Stefan Berger
Cc: David Howells
Cc: keyri...@vger.kernel.org
---
1 - 100 of 1492 matches
Mail list logo
