[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2828347.d8MXItvaOC@silver>
Date: Mon, 14 Sep 2020 13:06:34 +0200
From: Christian Schoenebeck <qemu_oss@...debyte.com>
To: Greg Kurz <groug@...d.org>
Cc: Jianyong Wu <jianyong.wu@....com>, ericvh@...il.com,
lucho@...kov.net, asmadeus@...ewreck.org,
v9fs-developer@...ts.sourceforge.net, justin.he@....com,
linux-kernel@...r.kernel.org
Subject: Re: [V9fs-developer] [PATCH RFC 0/4] 9p: fix open-unlink-f*syscall bug
On Montag, 14. September 2020 10:35:46 CEST Greg Kurz wrote:
> On Mon, 14 Sep 2020 11:37:50 +0800
>
> Jianyong Wu <jianyong.wu@....com> wrote:
> > open-unlink-f*syscall bug is a well-known bug in 9p, we try to fix the bug
> > in this patch set.
> > I take Eric's and Greg's patches which constiute the 1/4 - 3/4 of this
> > patch set as the main frame of the solution. In patch 4/4, I fix the fid
> > race issue exists in Greg's patch.
>
> IIRC some patches were needed on the QEMU side as well... I'm spending
> less time on 9pfs in QEMU, so Cc'ing the new maintainer:
>
> Christian Schoenebeck <qemu_oss@...debyte.com>
AFAICS this is about this old bug report:
https://bugs.launchpad.net/qemu/+bug/1336794
So yes, looks like this also requires changes to the 9pfs 'local' fs driver on
QEMU side:
https://lists.nongnu.org/archive/html/qemu-devel/2016-06/msg07586.html
Eric, Greg, would there be an easy way to establish QEMU test cases running
the 9pfs 'local' fs driver? Right now we only have 9pfs qtest cases for QEMU
which can only use the 'synth' driver, which is not helpful for such kind of
issues.
Best regards,
Christian Schoenebeck
Powered by blists - more mailing lists