From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH v3] 9pfs: deprecate 'proxy' backend
Date: Wed, 21 Jun 2023 16:16:46 +0200 [thread overview]
Message-ID: <1802263.gKGKeHe8zJ@silver> (raw)
In-Reply-To: <20230621154136.6e1f3f4b@bahia>
On Wednesday, June 21, 2023 3:41:36 PM CEST Greg Kurz wrote:
> On Wed, 21 Jun 2023 15:32:39 +0200
> Christian Schoenebeck <qemu_oss@crudebyte.com> wrote:
>
> > On Thursday, June 15, 2023 11:35:05 AM CEST Christian Schoenebeck wrote:
> > > On Saturday, June 10, 2023 3:39:44 PM CEST Christian Schoenebeck wrote:
> > > > As recent CVE-2023-2861 once again showed, the 9p 'proxy' fs driver is
in
> > > > bad shape. Using the 'proxy' backend was already discouraged for
safety
> > > > reasons before and we recommended to use the 'local' backend instead,
> > > > but now it is time to officially deprecate the 'proxy' backend.
> > > >
> > > > Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> >
> > Ping
> >
>
> It seems you missed the review I posted last week :
>
> https://patchew.org/QEMU/E1q7ytt-0005Fl-JX@lizzy.crudebyte.com/
#20230612165742.3333ea08@bahia
Oh, I never received your email. I'll check the logs what happened there.
I'll send a v4 with your suggestions, they make sense.
Do you want me to add your "for the records" comments as well in the
deprecation notice?
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2023-06-21 14:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 13:39 [PATCH v3] 9pfs: deprecate 'proxy' backend Christian Schoenebeck
2023-06-12 14:57 ` [SPAM] " Greg Kurz
2023-06-15 9:35 ` Christian Schoenebeck
2023-06-21 13:32 ` Christian Schoenebeck
2023-06-21 13:41 ` Greg Kurz
2023-06-21 14:16 ` Christian Schoenebeck [this message]
2023-06-21 14:58 ` Greg Kurz
2023-06-21 13:39 ` Daniel P. Berrangé
2023-06-21 13:46 ` Daniel P. Berrangé
2023-06-21 14:27 ` Christian Schoenebeck
2023-06-21 15:28 ` Daniel P. Berrangé
2023-06-21 16:44 ` Christian Schoenebeck
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=1802263.gKGKeHe8zJ@silver \
--to=qemu_oss@crudebyte.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 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).