From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: "Steven J. Magnani" <steve@digidescorp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fat: Fix non-atomic NFS i_pos read
Date: Sat, 30 Jun 2012 03:53:51 +0900 [thread overview]
Message-ID: <87395et0e8.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <1340993974.9826.4.camel@iscandar.digidescorp.com> (Steven J. Magnani's message of "Fri, 29 Jun 2012 13:19:34 -0500")
"Steven J. Magnani" <steve@digidescorp.com> writes:
>> Just curious, this happened on the real system? I recently heard about
>> NFS issue.
> Not that I'm aware of. Can you point me to any discussion of the NFS
> issue? I've spent a lot of time recently studying the FAT NFS
> implementation and come to the conclusion that it is extremely
> vulnerable to inode eviction. More to follow...
It is true, I also know NFS support of FAT is broken, but I'm not sure
if it was read-only. Sorry, recent report was by private email, not
public.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2012-06-29 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 17:19 [PATCH] fat: Fix non-atomic NFS i_pos read Steven J. Magnani
2012-06-29 18:06 ` OGAWA Hirofumi
2012-06-29 18:19 ` Steven J. Magnani
2012-06-29 18:53 ` OGAWA Hirofumi [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=87395et0e8.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@digidescorp.com \
/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