From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>,
Antonios Motakis <antonios.motakis@huawei.com>
Subject: Re: [Qemu-devel] virtfs/9p duplicate inodes
Date: Tue, 23 Apr 2019 16:40:57 +0200 [thread overview]
Message-ID: <7519361.8GXJqb1B4Y@silver> (raw)
In-Reply-To: <20190423134442.0549f427@bahia.lan>
On Dienstag, 23. April 2019 13:44:42 CEST Greg Kurz wrote:
> Hi Christian,
>
> Sorry for the late response. I'm quite busy on other topics these days...
Absolutely no problem. We probably all share the same fate of constant work
load on endless battle fields popping up everywhere. :-)
> > I intended to extend Antonios' patch set regarding 9p QID collisions with
> > the goal to make the ids constant beyond reboots by storing the qpp_table
> > as fs xattr.
>
> Hmm... why would you do that ? Even if some filesystems do have persistant
> inode numbers, it isn't mandatory AFAIK.
Mja, unfortunately I found that necessary, see my comment in patch 3 for the
background / reason:
https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg03755.html
And sorry that my patch set did not go out as one thread today. I vow
emendation. ;-)
Best regards,
Christian Schoenebeck
WARNING: multiple messages have this Message-ID (diff)
From: Christian Schoenebeck via Qemu-devel <qemu-devel@nongnu.org>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>,
Antonios Motakis <antonios.motakis@huawei.com>
Subject: Re: [Qemu-devel] virtfs/9p duplicate inodes
Date: Tue, 23 Apr 2019 16:40:57 +0200 [thread overview]
Message-ID: <7519361.8GXJqb1B4Y@silver> (raw)
Message-ID: <20190423144057.EYa3O2OeECcH9dzsEtxNy73Gy0LXDpStS9d2kBXCpT4@z> (raw)
In-Reply-To: <20190423134442.0549f427@bahia.lan>
On Dienstag, 23. April 2019 13:44:42 CEST Greg Kurz wrote:
> Hi Christian,
>
> Sorry for the late response. I'm quite busy on other topics these days...
Absolutely no problem. We probably all share the same fate of constant work
load on endless battle fields popping up everywhere. :-)
> > I intended to extend Antonios' patch set regarding 9p QID collisions with
> > the goal to make the ids constant beyond reboots by storing the qpp_table
> > as fs xattr.
>
> Hmm... why would you do that ? Even if some filesystems do have persistant
> inode numbers, it isn't mandatory AFAIK.
Mja, unfortunately I found that necessary, see my comment in patch 3 for the
background / reason:
https://lists.gnu.org/archive/html/qemu-devel/2019-04/msg03755.html
And sorry that my patch set did not go out as one thread today. I vow
emendation. ;-)
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2019-04-23 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3205397.r2gctG0f81@silver>
[not found] ` <20190330174751.1eb8e298@bahia.lan>
[not found] ` <3754934.J2WuGLFlGG@silver>
2019-04-20 22:41 ` [Qemu-devel] virtfs/9p duplicate inodes Christian Schoenebeck
2019-04-20 22:41 ` Christian Schoenebeck via Qemu-devel
2019-04-23 11:44 ` Greg Kurz
2019-04-23 14:40 ` Christian Schoenebeck [this message]
2019-04-23 14:40 ` Christian Schoenebeck via Qemu-devel
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=7519361.8GXJqb1B4Y@silver \
--to=qemu_oss@crudebyte.com \
--cc=antonios.motakis@huawei.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.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.