All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolaus Rath <Nikolaus@rath.org>
To: fuse-devel@lists.sourceforge.net,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: fuse: when are release requests queued?
Date: Thu, 25 May 2017 16:08:10 -0700	[thread overview]
Message-ID: <87a860r0v9.fsf@thinkpad.rath.org> (raw)

Hello,

I am trying to debug a sporadic test failure in libfuse
(https://github.com/libfuse/libfuse/issues/157).


Can someone tell me at which point the fuse kernel module will send a
RELEASE request to userspace? Is it possible that this is delayed until
after the close() syscall for the last fd has returned and userspace has
submitted a different fuse request for the same fs?


Looking at fs/fuse/file.c, it looks as if fuse_release() directly calls
fuse_request_send_background() to send the request. But at that point I
can no longer follow the code. Is it possible for another request to
sneak in at this point?

Furthermore, does the VFS call fuse_release() directly while handling
the close() syscall, or does this happen asynchronously later on?


Thanks!
-Nikolaus

-- 
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

             reply	other threads:[~2017-05-25 23:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 23:08 Nikolaus Rath [this message]
2017-05-26 15:17 ` [fuse-devel] fuse: when are release requests queued? David Butterfield
2017-05-26 23:11   ` Nikolaus Rath
2017-05-27  1:49     ` [fuse-devel] " Maxim Patlasov
2017-05-27  1:39 ` Maxim Patlasov
2017-05-29 16:49   ` Nikolaus Rath
2017-05-31 17:50     ` Maxim Patlasov
2017-05-31 19:19       ` Nikolaus Rath
2017-05-31 19:32         ` Maxim Patlasov
2017-05-31 19:41           ` Nikolaus Rath
     [not found]             ` <87inkgvmp0.fsf-Zv899e0YUSYPWKMTL/zdXNi2O/JbrIOy@public.gmane.org>
2017-05-31 19:51               ` Michael Theall
2017-05-31 20:34                 ` Nikolaus Rath
2017-05-31 20:23             ` [fuse-devel] " Maxim Patlasov
2017-05-31 20:31               ` Nikolaus Rath
2017-05-31 20:47                 ` Maxim Patlasov

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=87a860r0v9.fsf@thinkpad.rath.org \
    --to=nikolaus@rath.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.