From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751593AbWJSNHn (ORCPT ); Thu, 19 Oct 2006 09:07:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751598AbWJSNHn (ORCPT ); Thu, 19 Oct 2006 09:07:43 -0400 Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:22471 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S1751523AbWJSNHm (ORCPT ); Thu, 19 Oct 2006 09:07:42 -0400 Subject: Re: [PATCH] tty: ->signal->tty locking From: Alan Cox To: Peter Zijlstra Cc: linux-kernel , Andrew Morton , Oleg Nesterov , Prarit Bhargava , Chris Wright In-Reply-To: <1161260013.3036.92.camel@taijtu> References: <1161260013.3036.92.camel@taijtu> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 19 Oct 2006 14:09:55 +0100 Message-Id: <1161263396.17335.42.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 (2.6.2-1.fc5.5) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Ar Iau, 2006-10-19 am 14:13 +0200, ysgrifennodd Peter Zijlstra: > Fix the locking of signal->tty. > > Use ->sighand->siglock to protect ->signal->tty; this lock is already used > by most other members of ->signal/->sighand. And unless we are 'current' or > the tasklist_lock is held we need ->siglock to access ->signal anyway. Nice Acked-by: Alan Cox