On 1/17/20 4:28 PM, Dr. David Alan Gilbert wrote:
* Philippe Mathieu-Daudé (phi...@redhat.com) wrote:
On 12/12/19 5:39 PM, Dr. David Alan Gilbert (git) wrote:
From: Stefan Hajnoczi
When running with multiple threads it can be tricky to handle
FUSE_INIT/FUSE_DESTROY in parallel with other requ
* Philippe Mathieu-Daudé (phi...@redhat.com) wrote:
> On 12/12/19 5:39 PM, Dr. David Alan Gilbert (git) wrote:
> > From: Stefan Hajnoczi
> >
> > When running with multiple threads it can be tricky to handle
> > FUSE_INIT/FUSE_DESTROY in parallel with other request types or in
> > parallel with th
On 12/12/19 5:39 PM, Dr. David Alan Gilbert (git) wrote:
From: Stefan Hajnoczi
When running with multiple threads it can be tricky to handle
FUSE_INIT/FUSE_DESTROY in parallel with other request types or in
parallel with themselves. Serialize FUSE_INIT and FUSE_DESTROY so that
malicious client
* Masayoshi Mizuma (msys.miz...@gmail.com) wrote:
> On Thu, Dec 12, 2019 at 04:39:01PM +, Dr. David Alan Gilbert (git) wrote:
> > From: Stefan Hajnoczi
> >
> > When running with multiple threads it can be tricky to handle
> > FUSE_INIT/FUSE_DESTROY in parallel with other request types or in
>
On Thu, Dec 12, 2019 at 04:39:01PM +, Dr. David Alan Gilbert (git) wrote:
> From: Stefan Hajnoczi
>
> When running with multiple threads it can be tricky to handle
> FUSE_INIT/FUSE_DESTROY in parallel with other request types or in
> parallel with themselves. Serialize FUSE_INIT and FUSE_DES
From: Stefan Hajnoczi
When running with multiple threads it can be tricky to handle
FUSE_INIT/FUSE_DESTROY in parallel with other request types or in
parallel with themselves. Serialize FUSE_INIT and FUSE_DESTROY so that
malicious clients cannot trigger race conditions.
Signed-off-by: Stefan Ha
