Linux filesystem development
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd.schubert@fastmail.fm>
To: Han-Wen Nienhuys <hanwenn@gmail.com>
Cc: Joanne Koong <joannelkoong@gmail.com>,
	linux-fsdevel@vger.kernel.org, Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: Interrupt on readdirplus?
Date: Wed, 11 Sep 2024 18:42:35 +0200	[thread overview]
Message-ID: <e5eb669c-d465-495e-b27e-a712553db121@fastmail.fm> (raw)
In-Reply-To: <CAOw_e7Y49DRmVxEOPcAubtdzXzu6J-Z2wdkumxDs7OMHLRipbw@mail.gmail.com>



On 9/11/24 17:59, Han-Wen Nienhuys wrote:
> On Wed, Sep 11, 2024 at 3:06 PM Bernd Schubert
> <bernd.schubert@fastmail.fm> wrote:
>> I mean SIG_IGN, either at fuse server startup or at set in opendir and
>> unset in closedir, the latter is rather ugly for multi threaded fuse server.
> 
> This would work for my tests, where the FUSE server is the same
> process as the one opening the directory, but if that is not the case,
> the SIG_IGN would have to be set not on the server, but on the process
> accessing the filesystem, right?
> 

Oh right, won't help to do it in fuse server.

  reply	other threads:[~2024-09-11 16:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10 12:45 Interrupt on readdirplus? Han-Wen Nienhuys
2024-09-10 15:58 ` Bernd Schubert
2024-09-10 17:38   ` Han-Wen Nienhuys
2024-09-10 19:19     ` Bernd Schubert
2024-09-10 22:03     ` Joanne Koong
2024-09-11  9:47       ` Han-Wen Nienhuys
2024-09-11  9:51         ` Bernd Schubert
2024-09-11 10:07           ` Han-Wen Nienhuys
2024-09-11 10:31             ` Bernd Schubert
2024-09-11 12:08               ` Han-Wen Nienhuys
2024-09-11 13:06                 ` Bernd Schubert
2024-09-11 15:59                   ` Han-Wen Nienhuys
2024-09-11 16:42                     ` Bernd Schubert [this message]
2024-09-12 17:26                   ` Han-Wen Nienhuys
2024-09-12 17:48                     ` Bernd Schubert
2024-09-13 10:36                   ` Han-Wen Nienhuys

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=e5eb669c-d465-495e-b27e-a712553db121@fastmail.fm \
    --to=bernd.schubert@fastmail.fm \
    --cc=hanwenn@gmail.com \
    --cc=joannelkoong@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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