Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753900AbZGFSiL (ORCPT ); Mon, 6 Jul 2009 14:38:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752217AbZGFSh4 (ORCPT ); Mon, 6 Jul 2009 14:37:56 -0400 Received: from lvps87-230-0-242.dedicated.hosteurope.de ([87.230.0.242]:46547 "EHLO lvps87-230-0-242.dedicated.hosteurope.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751894AbZGFShz (ORCPT ); Mon, 6 Jul 2009 14:37:55 -0400 Cc: Herbert Xu , linux-kernel@vger.kernel.org, "David S. Miller" , netdev@vger.kernel.org Message-Id: <23E5FE2E-C893-4606-A2B7-07ACF0A7A0BE@it-loops.com> From: Michael Guntsche To: Alan Cox In-Reply-To: <20090706191852.3e138fc5@lxorguk.ukuu.org.uk> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Subject: Re: BUG: scheduling while atomic Date: Mon, 6 Jul 2009 20:37:56 +0200 References: <23AED400-6DA5-462F-94F0-BEE34AC08A7A@it-loops.com> <20090627140643.7140f6a9@lxorguk.ukuu.org.uk> <33C7D336-F062-47B3-9033-D3DC465F793C@it-loops.com> <20090706074333.GA17276@gondor.apana.org.au> <20090706083119.GA17782@gondor.apana.org.au> <20090706163239.3f557b45@lxorguk.ukuu.org.uk> <20090706181736.766b3e7c@lxorguk.ukuu.org.uk> <6BC3DACB-2179-4322-B270-475180CC8AA2@it-loops.com> <20090706191852.3e138fc5@lxorguk.ukuu.org.uk> X-Mailer: Apple Mail (2.935.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1119 Lines: 37 On Jul 6, 2009, at 20:18, Alan Cox wrote: > On Mon, 6 Jul 2009 20:07:34 +0200 > Michael Guntsche wrote: > >> >> On Jul 6, 2009, at 19:17, Alan Cox wrote: >> >>> This is the more drastic way of doing it. I had hoped to put this >>> off but >>> in fact it cleans stuff up enormously. This has had only basic >>> testing >>> but the underlying idea is to simply remove all the pty special >>> casing >>> that causes messes in the first place. >> >> >> Hi Alan, >> >> Must commit a6540f731d506d9e82444cf0020e716613d4c46c still be >> reverted >> with your patch or can it stay in? > > Herbert is (as usual ;)) correct that it should be reverted. No crashes with the reverted commit and Alan's patch on my hardware here. A Load Test that would trigger it after some seconds is now running for several minutes without any problems. Michael -- 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/