mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Haifeng Xu <haifeng.xu@shopee.com>
To: Bernd Schubert <bernd.schubert@fastmail.fm>,
	Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] fuse: do not generate interrupt requests for fatal signals
Date: Tue, 27 Aug 2024 16:46:03 +0800	[thread overview]
Message-ID: <12c30542-27bf-4e63-b4dc-1c9193863062@shopee.com> (raw)
In-Reply-To: <92427273-edeb-42b2-8f3c-5256d5a4b056@fastmail.fm>



On 2024/8/22 01:38, Bernd Schubert wrote:
> 
> 
> On 6/15/24 14:19, Haifeng Xu wrote:
>>
>>
>> On 2024/6/14 18:01, Miklos Szeredi wrote:
>>> On Thu, 13 Jun 2024 at 12:44, Haifeng Xu <haifeng.xu@shopee.com> wrote:
>>>
>>>> So why the client doesn't get woken up?
>>>
>>> Need to find out what the server (lxcfs) is doing.  Can you do a
>>> strace of lxcfs to see the communication on the fuse device?
>>
>> ok, I use strace to track one of the server threads. The output
>> can be seen in attachment. 
>>
>> FD: 6 DIR  /run/lxcfs/controllers/sys/fs/cgroup/
>> FD: 7 CHR  /dev/fuse
> 
> I had missed that there is an strace output. 
> Would it be possible that you describe your issue with all 
> details you have? There is a timeout patch now and it would probably solve your issue
> 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lore.kernel.org_all_20240813232241.2369855-2D1-2Djoannelkoong-40gmail.com_T_&d=DwICaQ&c=R1GFtfTqKXCFH-lgEPXWwic6stQkW4U7uVq33mt-crw&r=3uoFsejk1jN2oga47MZfph01lLGODc93n4Zqe7b0NRk&m=5Vvh_Xul4vraWltHaaiJGAV6x-UDqHBp5rxONeLnrrClC8HrZVWapSodWQUOIYiT&s=PsUk37fgf2VgSXOxE3UlYxu5su7eWMPCoErBzmRj2u0&e= 
> 
> 
> but Miklos is asking for a motivation. From point of view that fuse server could 
> abort requests itself Miklos is absolutely right (the product I'm actually working
> on has that...). And one could even add a timeout mechanism to libfuse.
> But question to understand your main issue and if there would be a request 
> timeout needed.
> 
> In general, it would be helpful if you could provide everything you know, already
> with the initial patch.
> Later on you posted that you use LXCFS, but personally I don't know anything about
> it. So it would be good to describe where that actually runs and what you do to trigger
> the issue, etc. Details...

In our production environment, this issuse happened serval times, but we don't know why the lxcfs server
didn't send reply to client(received SIGKILL). So if the fuse server can't abort the request, the client
thread will hung forever.

> 
> Thanks,
> Bernd

  reply	other threads:[~2024-08-27  8:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13  4:01 Haifeng Xu
2024-06-13  7:55 ` Miklos Szeredi
2024-06-13 10:44   ` Haifeng Xu
2024-06-14 10:01     ` Miklos Szeredi
2024-06-15 12:19       ` Haifeng Xu
2024-08-21 17:38         ` Bernd Schubert
2024-08-27  8:46           ` Haifeng Xu [this message]
2024-06-17  7:25       ` Christian Brauner
2024-06-20  6:43         ` Haifeng Xu
2024-06-20 21:40           ` Bernd Schubert
2024-06-21  2:36             ` Haifeng Xu
2024-06-14 10:31   ` Bernd Schubert
2024-06-15 12:20     ` Haifeng Xu

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=12c30542-27bf-4e63-b4dc-1c9193863062@shopee.com \
    --to=haifeng.xu@shopee.com \
    --cc=bernd.schubert@fastmail.fm \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®