Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265267AbUAESbO (ORCPT ); Mon, 5 Jan 2004 13:31:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265270AbUAESbO (ORCPT ); Mon, 5 Jan 2004 13:31:14 -0500 Received: from fw.osdl.org ([65.172.181.6]:50314 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S265267AbUAESbH (ORCPT ); Mon, 5 Jan 2004 13:31:07 -0500 Date: Mon, 5 Jan 2004 10:31:02 -0800 (PST) From: Linus Torvalds To: Markus =?ISO-8859-1?Q?H=E4stbacka?= cc: Kernel Mailinglist Subject: Re: 2.6.1-rc1 affected? In-Reply-To: <1073326471.21338.21.camel@midux> Message-ID: References: <1073320318.21198.2.camel@midux> <1073326471.21338.21.camel@midux> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 981 Lines: 24 On Mon, 5 Jan 2004, Markus H?stbacka wrote: > > Why isn't there any security update to 2.6.0/2.6.1-rc1 out yet, then? Because nobody actually contacted me about the problem and I read about it on linux-kernel like everybody else? Because I just got up and created the patch? And because nobody has an exploit yet, and one may be hard or impossible to create? And because people who care about these things tend to not update to x.0 kernels anyway? > But I think there's corporations who use 2.6.0 and don't read the lkml. They'll get a 2.6.1 soonish. The patch is in the current BK tree, will be in -rc2, and will be in 2.6.1. Let's just make sure we don't screw up the release due to being too much in a hurry either.. Linus - 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/