public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernardo Innocenti <bernie@develer.com>
To: Neil Conway <nconway_kernel@yahoo.co.uk>
Cc: Anders Saaby <as@cohaesio.com>,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	lkml <linux-kernel@vger.kernel.org>,
	nfs@lists.sourceforge.net
Subject: Re: NFS client bug in 2.6.8-2.6.11
Date: Wed, 16 Mar 2005 03:49:48 +0100	[thread overview]
Message-ID: <42379ECC.9060100@develer.com> (raw)
In-Reply-To: <20050315234415.71730.qmail@web26510.mail.ukl.yahoo.com>

Neil Conway wrote:

> 766 -> 770 sounds like a "small" (ish) number of patches to check, if
> we're lucky.  Did you wade through 'em all yet?  Any smoking guns?

The RPM changelog doesn't contain anything relevant
between 766 and 770:

---CUT---
* Thu Feb 24 2005 Dave Jones <davej@redhat.com>

- Use old scheme first when probing USB. (#145273)

* Wed Feb 23 2005 Dave Jones <davej@redhat.com>

- Try as you may, there's no escape from crap SCSI hardware. (#149402)

* Mon Feb 21 2005 Dave Jones <davej@redhat.com>

- Disable some experimental USB EHCI features.

* Tue Feb 15 2005 Dave Jones <davej@redhat.com>

- Fix bio leak in md layer.
---CUT---

Perhaps the changelog is incomplete.  I don't have the
two SRPMs at hand to make a comparison.

By the way, it seems upgrading to 2.6.10-1.770_FC3 just made
the bug much harder to trigger: I've definitely seen it once
again when I had left a shell sitting in an NFS directory
overnight.  I couldn't reproduce it a second time.


> PS: oh bugger, just remembered that I also reproduced my bug with a
> 2.6.8 kernel on the server; admittedly though it was an FC2 kernel so
> who knows what extra patches it had.

You can easily find out by downloading the SRPM.  Now that
Fedora provides a public CVS, perhaps it could be used to
make such investigations directly with the cvsweb interface
without downloading and unpacking a 40MB file.

-- 
  // Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/  http://www.develer.com/


  reply	other threads:[~2005-03-16  2:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 23:44 NFS client bug in 2.6.8-2.6.11 Neil Conway
2005-03-16  2:49 ` Bernardo Innocenti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-08  4:53 Bernardo Innocenti
2005-03-08  5:30 ` Trond Myklebust
2005-03-08  6:38   ` Bernardo Innocenti
2005-03-08  6:47     ` Trond Myklebust
2005-03-08  9:26       ` Bernardo Innocenti
2005-03-08  7:03     ` Bernardo Innocenti
2005-03-08  8:56       ` Anders Saaby
2005-03-08 22:25         ` Bernardo Innocenti

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=42379ECC.9060100@develer.com \
    --to=bernie@develer.com \
    --cc=as@cohaesio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nconway_kernel@yahoo.co.uk \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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