All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Bruin <jmdebruin@xmsnet.nl>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-nfs@vger.kernel.org
Subject: Re: 3.17.0+ files disappearing after playing old dos game on nfsroot laptop
Date: Fri, 01 May 2015 13:40:48 +0200	[thread overview]
Message-ID: <55436640.8080708@xmsnet.nl> (raw)
In-Reply-To: <87pp6kewzd.fsf@x220.int.ebiederm.org>

On 05/01/2015 06:35 AM, Eric W. Biederman wrote:
> Hans de Bruin <jmdebruin@xmsnet.nl> writes:
>
>>> I expect what needs to happen is to confirm that nfs directory entry
>>> revalidation is buggy, and at least for the short term re-add the nfs
>>> logic that will avoid dropping a dentry if it is a mount point, or
>>> path to a mount point, to avoid the nfs bugs.
>>>
>>
>> ok, I will go in waiting mode.
>
> I dropped the ball on this but it looks like someone else hit the
> problem and the following two commits fixed this issue:
>
> Can you confirm that things are working again?

I noticed the issue was gone in one of the previous releases. I was 
wondering whether you changed something or not. Sorry for not notifying you.

-- 
Hans


  reply	other threads:[~2015-05-01 11:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 20:00 3.17.0+ files disappearing after playing old dos game on nfsroot laptop Hans de Bruin
2014-10-19 17:32 ` Hans de Bruin
2014-10-24 16:07   ` Hans de Bruin
2014-10-24 16:25     ` Hans de Bruin
2014-10-24 18:18       ` Eric W. Biederman
2014-10-25 10:38         ` Hans de Bruin
2014-10-25 14:55           ` Eric W. Biederman
2014-10-25 22:03             ` Hans de Bruin
2015-05-01  4:35               ` Eric W. Biederman
2015-05-01 11:40                 ` Hans de Bruin [this message]
2015-05-01 21:45                   ` Eric W. Biederman

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=55436640.8080708@xmsnet.nl \
    --to=jmdebruin@xmsnet.nl \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.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 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.