linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Rees <rees@umich.edu>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: Re: bisecting an NFS issue prevented by fs/nfsd/nfs4recover.c:1414
Date: Wed, 7 Aug 2013 16:26:17 -0400	[thread overview]
Message-ID: <20130807202617.GA29924@umich.edu> (raw)
In-Reply-To: <5202AB04.9010006@gmx.de>

Toralf Förster wrote:

  I'm trying to bisect a NFS + EXT3/4 + loop device issue introduced
  probably between v3.8 and v3.10. Unfortunately my test systems (2 user
  mode linux images) often fails to reproduce the origin issue due to a
  crash in at another place.
  
  Now I'm wondering if somebody can point me to (few) patches, which I could
  just apply during bisect to avoid running into the "false" bug.

It could be this:

7255e71 nfsd: fix oops when legacy_recdir_name_error is passed a -ENOENT error

  reply	other threads:[~2013-08-07 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07 20:16 bisecting an NFS issue prevented by fs/nfsd/nfs4recover.c:1414 Toralf Förster
2013-08-07 20:26 ` Jim Rees [this message]
2013-08-08 16:07   ` Toralf Förster

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=20130807202617.GA29924@umich.edu \
    --to=rees@umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --cc=toralf.foerster@gmx.de \
    /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;
as well as URLs for NNTP newsgroup(s).