[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAC1kPDOyYyvvkJr3yX=j4JE3q-jQwUN7tdkOG55HFjy6wE+DeA@mail.gmail.com>
Date: Mon, 19 May 2025 13:57:54 +0800
From: Chen Linxuan <chenlinxuan@...ontech.com>
To: Amir Goldstein <amir73il@...il.com>
Cc: Chen Linxuan <chenlinxuan@...ontech.com>, Shuah Khan <shuah@...nel.org>,
Miklos Szeredi <miklos@...redi.hu>, zhanjun@...ontech.com, niecheng1@...ontech.com,
wentao@...ontech.com, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] selftests: Add functional test for the abort file in fusectl
On Thu, May 15, 2025 at 6:27 PM Amir Goldstein <amir73il@...il.com> wrote:
>
> On Thu, May 15, 2025 at 9:35 AM Chen Linxuan <chenlinxuan@...ontech.com> wrote:
> >
> > + ret = read(test_fd, path_buf, sizeof(path_buf));
> > + ASSERT_LT(ret, 0);
>
> Nice!
> I guess you could also verify errno == ENOTCONN or whatever it is
> in this case.
I am currently facing two issues:
1. I am not sure about the exact functions of max_background and
congestion_threshold. I have prepared a patch that adds documentation
for these two fields, which can be found here:
https://lore.kernel.org/all/20250514061703.483505-2-chenlinxuan@uniontech.com/
2. How should I test the "waiting" file? My current idea is to have my
FUSE daemon stay in a state where it does not respond to requests, and
then use some form of inter-process communication (maybe a Unix
socket?) to make it resume working. I am not sure if there is a better
approach.
Thanks,
Chen Linxuan.
Powered by blists - more mailing lists