From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] lib/rmobj.c: fix warning on FUSE fs
Date: Wed, 27 Apr 2016 16:29:44 +0300 [thread overview]
Message-ID: <5720BEC8.9040405@oracle.com> (raw)
In-Reply-To: <20160427121559.GB17331@rei.lan>
Hi,
On 04/27/2016 03:15 PM, Cyril Hrubis wrote:
> Hi!
>> This warning can appear on FUSE fs in cleanup():
>> TWARN : tst_tmpdir.c:219: tst_rmdir: rmobj(...) failed: unlink(
>> .../.fuse_hidden#####) failed; errno=2: No such file or directory
> Isn't this the same problem as the NFS one? I.e. unlinked but still open
> files?
No, checked syscalls/* tests, they all are closing fds before tst_rmdir().
It happens only if test does unlink(fd), then close(fd). If we change a test
so it calls close(fd) first, then unlink(fd), then ".fuse_hidden" never
being
created to store data about unlinked but still open file, and we won't have
this warning too. It's just another way to workaround it in the tests.
>
> But in this case it looks like the file was still there shortly after
> the fd has been closed, right? I wonder if that is a bug or not. I would
> expect that the file is no longer in the directory listing once the
> close() has returned from kernel.
Hmm, may be it is a bug, for a short period of time after close() we can
still have this temporary file listed. OK, I will check it with our
developers.
Thanks,
Alexey
prev parent reply other threads:[~2016-04-27 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 10:51 [LTP] [PATCH] lib/rmobj.c: fix warning on FUSE fs Alexey Kodanev
2016-04-27 12:15 ` Cyril Hrubis
2016-04-27 13:29 ` Alexey Kodanev [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=5720BEC8.9040405@oracle.com \
--to=alexey.kodanev@oracle.com \
--cc=ltp@lists.linux.it \
/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