Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755079Ab2BGGsN (ORCPT ); Tue, 7 Feb 2012 01:48:13 -0500 Received: from mail-bk0-f46.google.com ([209.85.214.46]:48877 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754070Ab2BGGsM (ORCPT ); Tue, 7 Feb 2012 01:48:12 -0500 Date: Tue, 7 Feb 2012 10:48:09 +0400 From: Anton Vorontsov To: Oleg Nesterov Cc: Greg KH , KOSAKI Motohiro , "Eric W. Biederman" , "Paul E. McKenney" , Paul Mundt , Russell King , Mike Frysinger , Benjamin Herrenschmidt , Richard Weinberger , linux-kernel@vger.kernel.org Subject: [PATCH 0/8] Fixes for common mistakes w/ for_each_process and task->mm Message-ID: <20120207064809.GA29061@oksana.dev.rtsoft.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 894 Lines: 27 Hi all, While working on lowmemorykiller driver, I stumbled upon several places where we traverse the tasklist in an unsafe manner, plus there are a few cases of unsafe access to task->mm. Note that some patches were not tested (e.g. sh, blackfin), so please take a closer look if there's silly mistakes. Also special attention needed for patch 7/8 (UML specific). Oleg, For sysrq case I kept the force_sig() usage, this is because in sysrq case I belive we do want to kill PID namespace init processes. If using force_sig() is still a bad idea, I guess we should fix it somehow else. Thanks. -- Anton Vorontsov Email: cbouatmailru@gmail.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/