From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Jim Rees <rees@umich.edu>
Cc: Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: Re: bisecting an NFS issue prevented by fs/nfsd/nfs4recover.c:1414
Date: Thu, 08 Aug 2013 18:07:13 +0200 [thread overview]
Message-ID: <5203C231.7030802@gmx.de> (raw)
In-Reply-To: <20130807202617.GA29924@umich.edu>
On 08/07/2013 10:26 PM, Jim Rees wrote:
> 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
>
ofc - thx
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
prev parent reply other threads:[~2013-08-08 16:07 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
2013-08-08 16:07 ` Toralf Förster [this message]
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=5203C231.7030802@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.