From: Bruce Guenter <bruce@untroubled.org>
To: linux-nfs@vger.kernel.org
Subject: Re: Invisible file problem
Date: Wed, 23 Feb 2011 08:50:04 -0600 [thread overview]
Message-ID: <20110223145004.GA6747@untroubled.org> (raw)
In-Reply-To: <1298447447.2968.8.camel@heimdal.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 498 bytes --]
On Tue, Feb 22, 2011 at 11:50:47PM -0800, Trond Myklebust wrote:
> There is a known bug in readdir that has been fixed in 2.6.38-rc6, but
> hasn't yet hit the 2.6.37 stable series. Please check the patch at
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git&a=commitdiff&h=d1205f87bbb8040c1408bbd9e0a720310b2b0b9b
>
> and see if it fixes your problem.
Yes it did, thank you very much.
--
Bruce Guenter <bruce@untroubled.org> http://untroubled.org/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-02-23 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 21:52 Invisible file problem Bruce Guenter
2011-02-23 7:50 ` Trond Myklebust
2011-02-23 14:50 ` Bruce Guenter [this message]
2011-02-23 19:42 ` Joe Landman
2011-02-23 20:23 ` Bruce Guenter
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=20110223145004.GA6747@untroubled.org \
--to=bruce@untroubled.org \
--cc=linux-nfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).