Difference between revisions of "Kernel bugs"

From CRIU
Jump to: navigation, search
Line 22: Line 22:
 
|20160512
 
|20160512
 
| kernfs: kernfs_sop_show_path: don't return 0 after seq_dentry call
 
| kernfs: kernfs_sop_show_path: don't return 0 after seq_dentry call
 +
|-
 +
|20160531
 +
| [http://www.spinics.net/lists/autofs/msg01174.html autofs: don't stuck in a loop if vfs_write returns an error]
 
|-
 
|-
 
|20161024
 
|20161024

Revision as of 03:54, 20 April 2017

We have implemented Travis CI setup (and were using Jenkins before) to check if any recent kernel changes break CRIU — before they appear in the vanilla 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
20140924 linux-next: cgroup_mount() falls asleep forever
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
20160531 autofs: don't stuck in a loop if vfs_write returns an error
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
20170321 linux-next: x86: Unable to run x32 processes on the x86_64 kernel
20170417 Re: cgroup: avoid attaching a cgroup root to two different superblocks
20170419 Re: irq/affinity: Fix extra vecs calculation

See also