Hi all,
On 11-08-19 09:43, Christoph Hellwig wrote:
On Sun, Aug 11, 2019 at 09:40:05AM +0200, Greg Kroah-Hartman wrote:
Since I do not see the lack of reviewing capacity problem get solved
anytime soon, I was wondering if you are ok with putting the code
in drivers/staging/vboxsf for now, until someone can review it and ack it
for moving over to sf/vboxsf ?
I have no objection to that if the vfs developers do not mind.
We had really bad experiences with fs code in staging. I think it is
a bad idea that should not be repeated.
So after resolving the problem with the patch not making it through
to the list because of the patch-size, v12 got reviewed (thank you
for that Christoph) and I did a v13.
Then there was some discussion about read cache-coherency vs writes
done on the host side underneath us (the guest) and in the end
Christoph agreed that what was done in v13 was as good as it would
get given the limitations of the shared folder API offered by
the VirtualBox hypervisor, but Christoph did request to add a big
comment explaining these issues in more detail.
So I posted a v14, adding the big comment and addressing 2 very minor
other issue spotted by Christoph, that was 10 days ago and things
have gotten quiet again since. I realiz that 10 days is not very
long but for previous revisions I have been waiting upto 60 days
sometimes and the exfat in staging discussion reminded me of this.
So what is the plan going forward for vboxsf now?
Regards,
Hans
