lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 10 Feb 2013 15:10:13 +0100 From: Frederic Weisbecker <fweisbec@...il.com> To: Li Zhong <zhong@...ux.vnet.ibm.com> Cc: linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org, paulmck@...ux.vnet.ibm.com, benh@...nel.crashing.org, paulus@...ba.org Subject: Re: [RFC PATCH 2/5] powerpc: Exception hooks for context tracking subsystem 2013/2/1 Li Zhong <zhong@...ux.vnet.ibm.com>: > This is the exception hooks for context tracking subsystem, including > data access, program check, single step, instruction breakpoint, machine check, > alignment, fp unavailable, altivec assist, unknown exception, whose handlers > might use RCU. > > This patch corresponds to > [PATCH] x86: Exception hooks for userspace RCU extended QS > commit 6ba3c97a38803883c2eee489505796cb0a727122 > > Signed-off-by: Li Zhong <zhong@...ux.vnet.ibm.com> Looks good! I guess we should move exception_enter/exit definition to the generic code. They should be the same for all archs after all. Also we are relying on user_mode(regs) but this may be buggy with some corner cases. For example if an exception happen after a call to user_exit() (on syscall exit) but before we actually resume in userspace, the exception will exit in kernel mode from the context tracking POV. So instead on relying on the regs, which are not sync with the context tracking state, we should use something like: prev_state = exception_enter(); ... exception_exit(prev_state); Also preempt_schedule_irq() is concerned as well by this problem. So I should convert it to that scheme as well. I'm going to prepare some patches. Feel free to merge this patch in the powerpc tree, I'll do the conversion along the way. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists