public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
	Jeff Garzik <jeff@garzik.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	NeilBrown <neilb@suse.de>, Adrian Bunk <bunk@stusta.de>
Subject: Re: [bisect] NFS regression breaks X
Date: Thu, 10 May 2007 09:36:44 -0400	[thread overview]
Message-ID: <46431FEC.7000901@oracle.com> (raw)
In-Reply-To: <1178755813.6760.26.camel@heimdal.trondhjem.org>

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

Trond Myklebust wrote:
> On Wed, 2007-05-09 at 15:52 -0700, Andrew Morton wrote:
>> It's a bit rough that Jeff spent a large amount of time hunting down an
>> already-known bug.  That's normally my job :(
> 
> The bug was reported by Florin Iucha (on lkml!) on Saturday. It has only
> just been debugged, and I was in fact in the middle of marshalling the
> fixes.
> 
>> This five-week-old diff only ever appeared in 2.6.21-mm1, which was
>> released four days ago.  It was then whizzed into mainline.  We thus lost
>> five weeks public testing which would probably have saved Jeff his pain.
>>
>> What went wrong?
> 
> Probably my fault. I've had a couple of weeks of heavy travel due to
> various circumstances that were beyond my control, and so I had little
> time in which to test the stuff and push it out.
> 
> Another factor that is affecting us is the slow but gradual collapse of
> the OSDL NFSv4 regression testing effort.

I had expected that many of these issues would be caught by the OSDL 
test harness.  I learned only yesterday that it was no longer available, 
so I am making an effort to broaden my personal test regime.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 291 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel/
version:2.1
end:vcard


  reply	other threads:[~2007-05-10 13:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09 21:30 [bisect] NFS regression breaks X Jeff Garzik
2007-05-09 21:51 ` Linus Torvalds
2007-05-09 22:17   ` Trond Myklebust
2007-05-09 22:48   ` Jeff Garzik
2007-05-09 22:03 ` Trond Myklebust
2007-05-09 22:52   ` Andrew Morton
2007-05-10  0:10     ` Trond Myklebust
2007-05-10 13:36       ` Chuck Lever [this message]
2007-05-11 22:54       ` Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46431FEC.7000901@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@stusta.de \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox