Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S275341AbTHNSi5 (ORCPT ); Thu, 14 Aug 2003 14:38:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S275345AbTHNSi4 (ORCPT ); Thu, 14 Aug 2003 14:38:56 -0400 Received: from mail.jlokier.co.uk ([81.29.64.88]:61312 "EHLO mail.jlokier.co.uk") by vger.kernel.org with ESMTP id S275341AbTHNSi1 (ORCPT ); Thu, 14 Aug 2003 14:38:27 -0400 Date: Thu, 14 Aug 2003 19:38:06 +0100 From: Jamie Lokier To: Linus Torvalds Cc: Roland McGrath , Andrew Morton , Matt Wilson , linux-kernel@vger.kernel.org, Ingo Molnar , Jeremy Fitzhardinge Subject: Re: [PATCH] revert zap_other_threads breakage, disallow CLONE_THREAD without CLONE_DETACHED Message-ID: <20030814183806.GA11703@mail.jlokier.co.uk> References: <20030814182757.GA11623@mail.jlokier.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 723 Lines: 17 Linus Torvalds wrote: > I've pushed the change to the BK trees, and if you're not a BK user you > can just test the attached patch directly to see if it affects you.. That's cool, I am not affected. Simply the documentation you mentioned, I felt someone who writes code using CLONE_THREAD in future should be aware that if they just use CLONE_THREAD by itself, their code won't work as expected with the later 2.5 kernels. The EINVAL ensures that perfectly. So, :) -- Jamie - 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/