From: Dominique Martinet <dominique.martinet@cea.fr>
To: Eric Van Hensbergen <ericvh@gmail.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Bug 1336794 <1336794@bugs.launchpad.net>,
qemu-devel <qemu-devel@nongnu.org>,
V9FS Developers <v9fs-developer@lists.sourceforge.net>
Subject: Re: [Qemu-devel] [V9fs-developer] [Bug 1336794] Re: 9pfs does not honor open file handles on unlinked files
Date: Wed, 15 Apr 2015 13:28:02 +0200 [thread overview]
Message-ID: <20150415112802.GA16121@u-blusson> (raw)
In-Reply-To: <CAFkjPTmwXgq6jJow=zBEuCzJ46mApOF5w8ETbZzh7Eycfg4hhQ@mail.gmail.com>
Eric Van Hensbergen wrote on Mon, Apr 13, 2015 at 04:05:28PM +0000:
> Well, technically fid 3 isn't 'open', only fid 2 is open - at least
> according to the protocol. fid 3 and fid 2 are both clones of fid 1.
Right, they're clone fids, but nothing in the protocol says what should
happen to non-open fids when you unlink the file either - I guess both
behaviours are OK as long as the client can handle it, so it would make
sense to at least call fstat() on the fid matching the fd, but while
I think this is how the kernel currently behaves the kernel doesn't HAVE
to make one open, separate fid per open file descriptor either.
> However, thanks for the alternative workaround. If you get a chance, can
> you check that my change to the client to partially fix this for the other
> servers doesn't break nfs-ganesha:
>
> https://github.com/ericvh/linux/commit/fddc7721d6d19e4e6be4905f37ade5b0521f4ed5
I'm afraid I haven't had much time lately, but while fstat-after-unlink
still works I'm getting some Oops with my basic test suite (create empty
files and rm -rf, kernel compilation, etc - nothing fancy) to the point
of locking myself out of my test box pretty quickly.
I'll try to debug patches a bit more individually (trying everything at
once isn't helping), but at the very least something is fishy
--
Dominique Martinet
next prev parent reply other threads:[~2015-04-15 11:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 13:52 [Qemu-devel] [Bug 1336794] [NEW] 9pfs does not honor open file handles on unlinked files Cole Robinson
2015-04-10 12:30 ` [Qemu-devel] [Bug 1336794] " Mark Glines
2015-04-12 12:42 ` Eric Van Hensbergen
2015-04-12 14:09 ` Al Viro
2015-04-12 19:08 ` Eric Van Hensbergen
2015-04-13 8:27 ` [Qemu-devel] [V9fs-developer] " Dominique Martinet
2015-04-13 16:05 ` Eric Van Hensbergen
2015-04-14 16:07 ` Al Viro
2015-04-14 16:19 ` Eric Van Hensbergen
2015-04-14 21:44 ` Al Viro
2015-04-15 11:28 ` Dominique Martinet [this message]
2015-04-15 14:17 ` Eric Van Hensbergen
2015-04-12 12:45 ` [Qemu-devel] " Eric Van Hensbergen
2016-05-05 20:54 ` Server Angels
2016-05-25 11:14 ` Greg Kurz
2016-05-25 11:51 ` Sean Keeney
2016-05-05 21:01 ` Server Angels
2016-05-24 14:43 ` Launchpad Bug Tracker
2016-06-02 11:59 ` Greg Kurz
2016-06-25 8:25 ` Greg Kurz
2016-06-25 9:24 ` Greg Kurz
2017-08-04 6:03 ` Maxim Kuvyrkov
2017-08-04 8:00 ` Greg Kurz
2018-11-26 21:47 ` Alexander Gretha
2018-11-27 8:07 ` Greg Kurz
2018-11-28 21:20 ` Alexander Gretha
2020-05-26 11:58 ` Greg Kurz
2020-05-27 6:03 ` Greg Kurz
2020-12-10 8:47 ` Thomas Huth
2020-12-10 11:48 ` Thomas Huth
2021-05-03 16:40 ` Thomas Huth
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=20150415112802.GA16121@u-blusson \
--to=dominique.martinet@cea.fr \
--cc=1336794@bugs.launchpad.net \
--cc=ericvh@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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).