From: Greg Kurz <groug@kaod.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL v2 0/8] 9p patches 2019-10-10
Date: Mon, 14 Oct 2019 17:46:26 +0200 [thread overview]
Message-ID: <20191014174626.76dc4e5c@bahia.lan> (raw)
In-Reply-To: <CAFEAcA8tdhYm0EuVGx5OiPv7NuZvrtrPLnK+tz=xoJ0Gn4DCmw@mail.gmail.com>
On Mon, 14 Oct 2019 15:08:52 +0100
Peter Maydell <peter.maydell@linaro.org> wrote:
> On Thu, 10 Oct 2019 at 14:18, Greg Kurz <groug@kaod.org> wrote:
> >
> > The following changes since commit 98b2e3c9ab3abfe476a2b02f8f51813edb90e72d:
> >
> > Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request' into staging (2019-10-08 16:08:35 +0100)
> >
> > are available in the Git repository at:
> >
> > https://github.com/gkurz/qemu.git tags/9p-next-2019-10-10
> >
> > for you to fetch changes up to e410bbc52a7a246858af54ce1842fadf26f39ff7:
> >
> > MAINTAINERS: Downgrade status of virtio-9p to "Odd Fixes" (2019-10-10 12:36:28 +0200)
> >
> > ----------------------------------------------------------------
> > The most notable change is that we now detect cross-device setups in the
> > host since it may cause inode number collision and mayhem in the guest.
> > A new fsdev property is added for the user to choose the appropriate
> > policy to handle that: either remap all inode numbers or fail I/Os to
> > another host device or just print out a warning (default behaviour).
> >
> > This is also my last PR as _active_ maintainer of 9pfs.
> >
> > ----------------------------------------------------------------
>
>
> Applied, thanks.
>
> Please update the changelog at https://wiki.qemu.org/ChangeLog/4.2
> for any user-visible changes.
>
> Thanks for all your work on the 9pfs code!
>
Thanks Peter, and many others, for your valuable help.
As now indicated in MAINTAINERS, I'll stay around for odd fixes, one
of which that comes to mind is to deprecate the "proxy" backend and
its companion virtfs-proxy-helper binary at some point since it isn't
supported by libvirt and will be superseded soon by "virtio-fs".
Cheers,
--
Greg
> -- PMM
prev parent reply other threads:[~2019-10-14 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 13:18 [PULL v2 0/8] 9p patches 2019-10-10 Greg Kurz
2019-10-10 13:18 ` [PULL v2 1/8] 9p: unsigned type for type, version, path Greg Kurz
2019-10-10 13:18 ` [PULL v2 2/8] 9p: Simplify error path of v9fs_device_realize_common() Greg Kurz
2019-10-10 13:18 ` [PULL v2 3/8] fsdev: Add return value to fsdev_throttle_parse_opts() Greg Kurz
2019-10-10 13:18 ` [PULL v2 4/8] 9p: Treat multiple devices on one export as an error Greg Kurz
2019-10-10 13:18 ` [PULL v2 5/8] 9p: Added virtfs option 'multidevs=remap|forbid|warn' Greg Kurz
2019-10-10 13:18 ` [PULL v2 6/8] 9p: stat_to_qid: implement slow path Greg Kurz
2019-10-10 13:18 ` [PULL v2 7/8] 9p: Use variable length suffixes for inode remapping Greg Kurz
2019-10-10 13:18 ` [PULL v2 8/8] MAINTAINERS: Downgrade status of virtio-9p to "Odd Fixes" Greg Kurz
2019-10-14 14:08 ` [PULL v2 0/8] 9p patches 2019-10-10 Peter Maydell
2019-10-14 15:46 ` Greg Kurz [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=20191014174626.76dc4e5c@bahia.lan \
--to=groug@kaod.org \
--cc=peter.maydell@linaro.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 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).