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: Sat, 3 Nov 2012 16:03:21 +0800 From: Cyberman Wu <cypher.w@...il.com> To: linux-kernel@...r.kernel.org Subject: Is this a kernel bug? Recent days we got a exception in kernel thread [kworker/n:m], but exception handler call do_group_exit() -> do_exit() -> schedule() and got another exception in schedule(): /* * If a worker is going to sleep, notify and * ask workqueue whether it wants to wake up a * task to maintain concurrency. If so, wake * up the task. */ if (prev->flags & PF_WQ_WORKER) { struct task_struct *to_wakeup; to_wakeup = wq_worker_sleeping(prev, cpu); if (to_wakeup) try_to_wake_up_local(to_wakeup); } Exception occurred while wq_worker_sleeping() -> kthread_data(). It's because do_exit() -> exit_mm() -> mm_release(): /* notify parent sleeping on vfork() */ if (vfork_done) { tsk->vfork_done = NULL; complete(vfork_done); } I'm using a patched version of kernel 2.6.38.8. But I've checked code of kernel version 3.6.5, it seems have the same process, only with files and functions split. -- Cyberman Wu -- 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