From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Bottomley Subject: Re: [Bug #12195] "dd" make kernel panic Date: Sun, 21 Dec 2008 08:52:22 -0500 Message-ID: <1229867542.3444.0.camel@localhost.localdomain> References: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , Kernel Testers List , alexs , Lin Ming , Michael Anderson , Yanmin Zhang On Sat, 2008-12-20 at 23:00 +0100, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.27. Please verify if it still should be listed and let me know > (either way). No ... it's fixed and upstream. James From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753931AbYLUNwY (ORCPT ); Sun, 21 Dec 2008 08:52:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752060AbYLUNwP (ORCPT ); Sun, 21 Dec 2008 08:52:15 -0500 Received: from accolon.hansenpartnership.com ([76.243.235.52]:35828 "EHLO accolon.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751899AbYLUNwO (ORCPT ); Sun, 21 Dec 2008 08:52:14 -0500 Subject: Re: [Bug #12195] "dd" make kernel panic From: James Bottomley To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , Kernel Testers List , alexs , Lin Ming , Michael Anderson , Yanmin Zhang In-Reply-To: References: Content-Type: text/plain Date: Sun, 21 Dec 2008 08:52:22 -0500 Message-Id: <1229867542.3444.0.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2008-12-20 at 23:00 +0100, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.27. Please verify if it still should be listed and let me know > (either way). No ... it's fixed and upstream. James