Difference between revisions of "Kernel bugs"

From CRIU
Jump to: navigation, search
(add preliminary text; add table heading; make the table sortable)
(Found bugs)
Line 32: Line 32:
 
| [https://lkml.org/lkml/2017/1/24/797 seccomp: dump core when using SECCOMP_RET_KILL]
 
| [https://lkml.org/lkml/2017/1/24/797 seccomp: dump core when using SECCOMP_RET_KILL]
 
|-
 
|-
 +
|20170310
 +
|[https://lkml.org/lkml/2017/3/10/1422 linux-next: WARNING: CPU: 1 PID: 24110 at fs/dcache.c:1445 umount_check+0x81/0x90]
 +
|-
 +
| 20170310
 +
|[http://marc.info/?l=linux-raid&m=148917926532636&w=2 linux-next: WARNING: CPU: 0 PID: 1 at lib/refcount.c:114 refcount_inc+0x37/0x40]
 
|}
 
|}
  
 
[[Category:Testing]]
 
[[Category:Testing]]

Revision as of 20:59, 10 March 2017

We have the CRIU-linux-next job to check all kernel changes before they move into the upstream kernel.

Found bugs

This table lists the linux-next kernel bugs found using CI.

Note that the list is incomplete; there were about a dozen bugs found and fixed before we started documenting it here.

Date Bug description
20150316 tcp_metrics: fix wrong lockdep annotations
20150928 skbuff: Fix skb checksum partial check.
20160512 kernfs: kernfs_sop_show_path: don't return 0 after seq_dentry call
20161024 mm: Add a user_ns owner to mm_struct and fix ptrace_may_access
20161114 BUG: unable to handle kernel NULL pointer dereference in __sk_mem_raise_allocated()
20161114 linux-next: net->netns_ids is used after calling idr_destroy for it
20170124 seccomp: dump core when using SECCOMP_RET_KILL
20170310 linux-next: WARNING: CPU: 1 PID: 24110 at fs/dcache.c:1445 umount_check+0x81/0x90
20170310 linux-next: WARNING: CPU: 0 PID: 1 at lib/refcount.c:114 refcount_inc+0x37/0x40