[PATCH] RCU: Adjust the comment of function rcu_is_watching

From: Zhouyi Zhou Because RCU avoids interrupting idle CPUs, rcu_is_watching is used to test whether or not it is currently legal to run RCU read-side critical sections on this CPU. First sentence and last sentence of current comment for rcu_is_watching have opposite meaning of what is

[PATCH] RCU: Adjust the comment of function rcu_is_watching

From: Zhouyi Zhou Because RCU avoids interrupting idle CPUs, rcu_is_watching is used to test whether or not it is currently legal to run RCU read-side critical sections on this CPU. First sentence and last sentence of current comment for rcu_is_watching have opposite meaning of what is

[PATCH] srcu: remove never used variable

From: Zhouyi Zhou In function srcu_gp_end, the variable idxnext is never used after assign, remove it and its assign statement. Signed-off-by: Zhouyi Zhou --- kernel/rcu/srcutree.c | 2 -- 1 file changed, 2 deletions(-) diff --git

[PATCH] srcu: remove never used variable

From: Zhouyi Zhou In function srcu_gp_end, the variable idxnext is never used after assign, remove it and its assign statement. Signed-off-by: Zhouyi Zhou --- kernel/rcu/srcutree.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c index

[PATCH] FS: EXT4: syn error in __ext4_grp_locked_error

From: Zhouyi Zhou In function __ext4_grp_locked_error, __save_error_info is called to save error info in super block block, but does not sync that information to disk to info the subsequence fsck after reboot. This patch sync the error information to disk. After this

[PATCH] FS: EXT4: syn error in __ext4_grp_locked_error

From: Zhouyi Zhou In function __ext4_grp_locked_error, __save_error_info is called to save error info in super block block, but does not sync that information to disk to info the subsequence fsck after reboot. This patch sync the error information to disk. After this patch, I think there is

[PATCH 1/1] kasan: fix livelock in qlist_move_cache

From: Zhouyi Zhou This patch fix livelock by conditionally release cpu to let others has a chance to run. Tested on x86_64. Signed-off-by: Zhouyi Zhou --- mm/kasan/quarantine.c | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff

[PATCH 1/1] kasan: fix livelock in qlist_move_cache

From: Zhouyi Zhou This patch fix livelock by conditionally release cpu to let others has a chance to run. Tested on x86_64. Signed-off-by: Zhouyi Zhou --- mm/kasan/quarantine.c | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/mm/kasan/quarantine.c

[PATCH RFC] ACPI: (x86) remove useless initial assignment in gsi_to_irq

From: Zhouyi Zhou I think in function gsi_to_irq, initial assignment to irq is useless although compiler may eliminate it during the compilng. Signed-off-by: Zhouyi Zhou --- arch/x86/kernel/acpi/boot.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH RFC] ACPI: (x86) remove useless initial assignment in gsi_to_irq

From: Zhouyi Zhou zhouzho...@gmail.com I think in function gsi_to_irq, initial assignment to irq is useless although compiler may eliminate it during the compilng. Signed-off-by: Zhouyi Zhou yizhouz...@ict.ac.cn --- arch/x86/kernel/acpi/boot.c |2 +- 1 file changed, 1 insertion(+), 1

re: ping: re:[PATCH 1/1] kernel code that do not handle NULL return of kmem_cache_zalloc

From: Zhouyi Zhou the text of previous ping message maybe garbled sorry for the trouble > I do a grep for kmem_cache_zalloc and kmem_cache_alloc > in kernel tree, and find some code do not handle NULL > return of kmem_cache_zalloc correctly > Signed-off-by: Zhouyi Zhou ---

re: ping: re:[PATCH 1/1] kernel code that do not handle NULL return of kmem_cache_zalloc

From: Zhouyi Zhou zhouzho...@gmail.com the text of previous ping message maybe garbled sorry for the trouble I do a grep for kmem_cache_zalloc and kmem_cache_alloc in kernel tree, and find some code do not handle NULL return of kmem_cache_zalloc correctly Signed-off-by: Zhouyi Zhou

[PATCH 1/1 v1] the recommended crash memory reservation is too small for x86_64.

From: root On Documentation/kdump/kdump.txt, section Boot into System Kernel: On x86 and x86_64, use "crashkernel=64M@16M", but some OSes like ubuntu 12.10 use ram fs larger than 64M, so in these cases the memory reserved for crashkernel should be at least 128M. Signed-off-by: Zhouyi

[PATCH 1/1 v1] the recommended crash memory reservation is too small for x86_64.

From: root root@zzy-Lenovo.(none) On Documentation/kdump/kdump.txt, section Boot into System Kernel: On x86 and x86_64, use crashkernel=64M@16M, but some OSes like ubuntu 12.10 use ram fs larger than 64M, so in these cases the memory reserved for crashkernel should be at least 128M.