On 1/4/2021 1:21 PM, Herbert Xu wrote:
On Sun, Jan 03, 2021 at 02:37:42AM +0800, kernel test robot wrote:
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot
All errors (new ones prefixed by >>):
ERROR: ".kmem_cache_alloc" [net/nfc/nfc.ko] unde
On 10/30/2020 9:17 PM, Matthew Wilcox wrote:
On Fri, Oct 30, 2020 at 03:17:15PM +0800, kernel test robot wrote:
Details are as below:
-->
To reproduce:
git clone https://github.com/inte
On 10/29/2020 11:28 PM, Andrey Konovalov wrote:
On Sun, Oct 25, 2020 at 8:17 PM Andrew Morton wrote:
On Mon, 26 Oct 2020 02:15:37 +0800 kernel test robot wrote:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: d76913908102044f14381df865bb74df17a5
On 10/15/2020 5:12 PM, Jan Kara wrote:
On Thu 15-10-20 11:08:43, Jan Kara wrote:
On Thu 15-10-20 08:46:01, NeilBrown wrote:
On Wed, Oct 14 2020, Jan Kara wrote:
On Wed 14-10-20 16:47:06, kernel test robot wrote:
Greeting,
FYI, we noticed a -15.3% regression of will-it-scale.per_process_o
On 9/30/2020 8:41 PM, Michael Petlan wrote:
Hello. To me, it looks rather a random failure. Is it actually reproducible
and proven that the patch has caused it? The patch doesn't seem to cause
the fails below.
Hi Michael,
It's not always reproducible, but we can reproduce it in most cases:
Thanks for the input, we do detect this on this commit but not its parent.
It may be merged into a wrong base branch or something else that
we are not aware of. And it's kind difficulty now for us to provide a
reproduction step for kexec issue, we will consider this further.
Best Regards,
Rong Ch
On 9/2/2020 12:27 AM, Paul E. McKenney wrote:
On Tue, Sep 01, 2020 at 03:03:28PM +0800, Rong Chen wrote:
On 8/31/20 11:50 PM, Paul E. McKenney wrote:
On Mon, Aug 31, 2020 at 08:01:22PM +0800, kernel test robot wrote:
Greeting,
FYI, we noticed the following commit (built with gcc-9):
comm
On 8/17/2020 6:28 PM, Tony Lindgren wrote:
Hi,
* kernel test robot [200811 11:55]:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 00e4db51259a5f936fec1424b884f029479d3981
commit: 35fba0f0fd762a8b87d403ae3c723e0061c4aa25 wlcore: Use spin_trylock in
On 6/19/2020 8:26 AM, Jason Gunthorpe wrote:
On Sat, Jun 13, 2020 at 04:19:03AM +0800, kernel test robot wrote:
Fixes: 8a69220b659c ("RDMA/qedr: Fix synchronization methods and memory leaks in
qedr")
Signed-off-by: kernel test robot
---
qedr_iw_cm.c |2 +-
1 file changed, 1 insertion
On 6/5/2020 10:05 PM, Peter Zijlstra wrote:
On Fri, Jun 05, 2020 at 06:17:51AM -0700, Eric Dumazet wrote:
On Fri, Jun 5, 2020 at 1:10 AM kernel test robot wrote:
There you go.
We decided this was a bogus report, and that UBSAN requires sane compilers.
Please read the fine comment that was
On 4/29/2020 11:28 AM, Anshuman Khandual wrote:
On 04/28/2020 02:51 PM, Catalin Marinas wrote:
On Tue, Apr 28, 2020 at 04:41:11AM -0400, Qian Cai wrote:
On Apr 28, 2020, at 1:54 AM, Anshuman Khandual
wrote:
That is true. There is a slight change in the rules, making it explicit yes
only
Tested-by: kernel test robot
On 10/23/2019 12:46 AM, Vincent Guittot wrote:
The task, for which the scheduler looks for the idlest group of CPUs, must
be discounted from all statistics in order to get a fair comparison
between groups. This includes utilization, load, nr_running and idle_cpus.
Hi Geert,
Thanks for your clarification. we are on vacation this week, and we'll
take a look asap.
Best Regards,
Rong Chen
On 10/2/2019 7:28 PM, Geert Uytterhoeven wrote:
Hi Kbuild test robot,
On Wed, Oct 2, 2019 at 11:53 AM kbuild test robot wrote:
I love your patch! Yet something to imp
On 4/1/2019 10:29 PM, Qu Wenruo wrote:
On 2019/4/1 下午10:02, Chen, Rong A wrote:
On 4/1/2019 9:28 PM, Nikolay Borisov wrote:
On 1.04.19 г. 16:24 ч., kernel test robot wrote:
FYI, we noticed the following commit (built with gcc-7):
commit: 70d28b0e4f8ed2d38571e7b1f9bec7f321a53102 ("
On 4/1/2019 9:28 PM, Nikolay Borisov wrote:
On 1.04.19 г. 16:24 ч., kernel test robot wrote:
FYI, we noticed the following commit (built with gcc-7):
commit: 70d28b0e4f8ed2d38571e7b1f9bec7f321a53102 ("btrfs: tree-checker: Verify dev
item")
https://git.kernel.org/cgit/linux/kernel/git/next/l
Hi all,
Kernel test robot reported a will-it-scale.per_thread_ops -64.1% regression on
IVB-desktop for v4.20-rc1.
The first bad commit is: 9bc8039e715da3b53dbac89525323a9f2f69b7b5, Yang Shi
: mm: brk: downgrade mmap_sem to read when shrinking
(https://lists.01.org/pipermail/lkp/2018-November/009
Hi, all
this is a bug of 0day environment, please ignore the report.
Thanks,
Rong, Chen
-Original Message-
From: LKP [mailto:lkp-boun...@lists.01.org] On Behalf Of kernel test robot
Sent: Sunday, July 22, 2018 3:42 PM
To: Dominique Martinet
Cc: l...@01.org; lkp ; LKML
Subject: [LKP] [l
ving the DEBUG macro makes the test always pass.
Signed-off-by: Chen Rong
---
tools/testing/selftests/bpf/dev_cgroup.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/tools/testing/selftests/bpf/dev_cgroup.c
b/tools/testing/selftests/bpf/dev_cgroup.c
index ce41a34..a167c6d 100644
--- a/too
18 matches
Mail list logo