From: Leonid Fedorenchik <leonid.fedorenchik@paragon-software.com>
To: "Kornievskaia, Olga" <Olga.Kornievskaia@netapp.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: help with understanding evict inode functionality
Date: Fri, 2 Oct 2015 16:57:10 +0300 [thread overview]
Message-ID: <560E8D36.7010803@paragon-software.com> (raw)
On Thu, 1 Oct 2015 22:54:08 +0000
"Kornievskaia, Olga" <Olga.Kornievskaia@netapp.com> wrote:
> [...]
>
> In NFS development, we’ve been seeing a race between reopening of the same file and evict inode code and unable figure out how to prevent such race. When file is opened for the first timed and then closed. As the last reference is dropped and iput_final() calls evict() which will call filesystem specific evict_inode() code. As that’s happening a new open for the same file is happening and causes problems.
Recently we encountered similar situation with NFS, that is, after
evict_inode() & iget_locked() we were getting the same inode (same
i->i_ino) and without I_NEW bit set.
>
> Also can somebody suggest how to debug VFS code, as putting printks generates output for the local filesystem code as well.
You can call printk() only if current process is "nfsd" (at least,
that is what we did).
>
> Thank you.
>
> [...]
--
Best regards,
Leonid Fedorenchik
Software Engineer
Paragon Software Group
Skype: leonid.fedorenchik
http://www.paragon-software.com
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-10-02 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 13:57 Leonid Fedorenchik [this message]
2015-10-02 14:38 ` help with understanding evict inode functionality Kornievskaia, Olga
2015-10-04 2:28 ` Theodore Ts'o
2015-10-04 6:01 ` Christoph Hellwig
2015-10-04 22:37 ` Theodore Ts'o
2015-10-15 9:53 ` Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2015-10-01 22:54 Kornievskaia, Olga
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=560E8D36.7010803@paragon-software.com \
--to=leonid.fedorenchik@paragon-software.com \
--cc=Olga.Kornievskaia@netapp.com \
--cc=linux-fsdevel@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).